Igor Obradovic wrote:
Hi,Yes, the reason is becuase you can only set the _UNICODE parameter when creating the database instance, not afterwards. And since setting DEFAULT_CODE to unicode requires _UNICODE to be true, the operation will fail.
I've installed SAP DB Version 7.4.03
on Windows XP professional.
Installation passed OK, without any problem.
But when I wanted to install a database instance
I encountered two problems.
First, with WebDBM I couldn't change parameters
_UNICODE and DEFAULT_CODE.
When I try to change them,
I always receive the message that the parameter is read only
and I cannot change values.
Then I tried to do a workaround, since it is important
to me that the database has unicode support.
I let WebDBM to create default parameter files
and after that, I edited them and manually and changed values for _UNICODE and DEFAULT_CODE
to YES and UNICODE respectively,
before I actually started installation.
But then a new problem arose there.
I received either -24974: ERR_XPSESSION - param session active
and I couldn't move to the next step
or I went to the end and started installation
but in the middle of installation process
I received -24988: ERR_SQL - sql error.
Anyway, when I install ASCII database everything is just fine,
but any time I want to install Unicode it becomes somehow impossible...
Is there any solution for this problem?
Anyone who can explain how to proceed
with installation in order to have a Unicode support?
Is it the problem of WebDBM maybe,
since I noticed that other people use unicode SapDBs?
The solution is to recreade the database instance with _UNICODE set to true.
Hope this helps
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
