Can't start SAP after Java add-in installation

[jonlarruzea]

Hi,

We have migrated our BW 3.1C system to BI 7.0 (Win2003, Oracle 10.2, non-unicode). Everything was OK with the Abap system upgrade. Now we are making a BI Java installation over the BI 7.0 Abap system (Java add-in installation). We have made the first step, SCS instance installation and now the SAP BI 7.0 abap system doesn't startup.

The workprocess fail to connect to Oracle and don't startup:

-

---

M Fri Dec 07 22:47:00 2007

M calling db_connect ...

C dbs/ora/array_buf_size = 650000

C Prepending F:\usr\sap\BWK\SYS\exe\run to Path.

C Oracle Client Version: '10.2.0.1.0'

C *** ERROR => OCI-call 'OCIEnvCreate' failed: rc = -1

[dboci.c 2159]

C *** ERROR => OCI-call 'OCIErrorGet' failed: rc = -2

[dboci.c 1986]

B ***LOG BY2=> sql error -1 performing CON [dbsh#2 @ 1204] [dbsh 1204 ]

B ***LOG BY0=> Cannot get Oracle error text. [dbsh#2 @ 1204] [dbsh 1204 ]

B ***LOG BY2=> sql error -1 performing CON [dblink#3 @ 431] [dblink 0431 ]

B ***LOG BY0=> Cannot get Oracle error text. [dblink#3 @ 431] [dblink 0431 ]

M ***LOG R19=> ThInit, db_connect ( DB-Connect 000256) [thxxhead.c 1411]

M in_ThErrHandle: 1

M *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c 10169]

-

---

Any idea about how to solve the problem?

Thanks in advance!

[markus_doehr2 · Accepted solution]

Additionally, your Oracle Instantclient is not supported also (you need to install 10.2.0.2), 10.2.0.1 is not supported.

--

Markus

[jonlarruzea · Accepted solution]

Hi Markus,

Yes, our Oracle server version is 10.2.0.2.

According to note "669902" the add-in installation of a SAP J2EE server into an existing SAP non-unicode system should be possible. Are you completely sure that this is not possible?

Thanks in advance.

[markus_doehr2 · Accepted solution]

Iu00B4m not talking about your Oracle server, Iu00B4m talking about your Oracle Instantclient:

M Fri Dec 07 22:47:00 2007

M calling db_connect ...

C dbs/ora/array_buf_size = 650000

C Prepending F:\usr\sap\BWK\SYS\exe\run to Path.

C Oracle Client Version: '10.2.0.1.0'

That version is not supported.

See note 998004 - Update the Oracle Instant Client on Windows

Iu00B4d do that as soon as possible, 10.2.0.1 has some real strange bugs.

Technically itu00B4s possible to install a Java AddIn into a non-Unicode system but it will lead to all sorts of problems if a person at the frontend enters characters, that are not supported in the backend system (and thus destroying the data). SAP supported that some time but it was deprecated due to that.

--

Markus

[jonlarruzea · Accepted solution]

Hi Markus,

Thanks for all your help. We will update the Oracle client as soon as possible. We will consider too the possible problems of a BI Java add-in installation in a BI non-unicode system. At the moment we are just upgrading our Integration server so we can test it before upgrading our Production server.

The problem is that we have scheduled a BI 7.0 learning for our users in our BI Integration system, so we must end with the BI Java add-in installatoin asap.

Our BI 7.0 Abap system started correctly with the Oracle 10.2.0.1 client so I don't think that upgrading it will solve the problem (anyway as already explained we will update it as soon as possible)...

So, any idea about why the work processes fail to connect to Oracle?? If we execute for example brconnect it connects correctly to Oracle...

Thanks again and best regards,

Jon

[markus_doehr2 · Accepted solution]

This may be the result of the old client or wrong NLS settings or both. Another reason may be a too old kernel and/or libdbora.dll.

Get your system up to the latest patchlevels (kernel et al).

Is this a 32bit windows?

--

Markus

[jonlarruzea · Accepted solution]

Hi Markus,

Thanks again for your help.

Yes, it is a 32 bit Win2003 server. We already upgraded to the last available version of the non-unicode 7.00 kernel (patch 114) and dboraslib.dll, but we continue with the same problem...

Thanks again,

Jon

[markus_doehr2 · Accepted solution]

What do you see in the trace file?

Is the environment ORA_NLS33 set? It must NOT be set.

--

Markus

[jonlarruzea · Accepted solution]

Hi,

ORA_NLS33 is not set as environment variable. We uninstalled the J2EE so now everything should be non-unicode and SAP should startup but we continue with the same error.

Some more info...

DW log info when everything was ok:

-

---

M calling db_connect ...

C dbs/ora/array_buf_size = 650000

C CLIENT_ORACLE_HOME is not set as environment variable or

C DIR_CLIENT_ORAHOME is not set as profile parameter.

C assuming using instant client with unspecified location.

C Oracle Client Version: '10.2.0.1.0'

C Client NLS settings: AMERICAN_AMERICA.WE8DEC

C Logon as OPS$-user to get SAPBWT's password

C Connecting as /@BWK on connection 0 (nls_hdl 0) ... (dbsl 700 110706)

C Nls CharacterSet NationalCharSet C EnvHp ErrHp ErrHpBatch

C 0 WE8DEC 1 048D7FA8 0BD02454 0BD01CDC

C Attaching to DB Server BWK (con_hdl=0,svchp=0BD01C28,svrhp=0BD04A24)

C Starting user session (con_hdl=0,svchp=0BD01C28,srvhp=0BD04A24,usrhp=0BD25D68)

C

C Thu Dec 06 18:00:20 2007

C Now '/@BWK' is connected (con_hdl 0, nls_hdl 0).

-

---

Actual DW log with the errors:

-

---

M calling db_connect ...

C dbs/ora/array_buf_size = 650000

C CLIENT_ORACLE_HOME is not set as environment variable or

C DIR_CLIENT_ORAHOME is not set as profile parameter.

C assuming using instant client with unspecified location.

C Oracle Client Version: '10.2.0.1.0'

C *** ERROR => OCI-call 'OCIEnvCreate' failed: rc = -1

[dboci.c 2159]

C *** ERROR => OCI-call 'OCIErrorGet' failed: rc = -2

[dboci.c 1986]

B ***LOG BY2=> sql error -1 performing CON [dbsh#2 @ 1204] [dbsh 1204 ]

B ***LOG BY0=> Cannot get Oracle error text. [dbsh#2 @ 1204] [dbsh 1204 ]

B ***LOG BY2=> sql error -1 performing CON [dblink#3 @ 431] [dblink 0431 ]

B ***LOG BY0=> Cannot get Oracle error text. [dblink#3 @ 431] [dblink 0431 ]

M ***LOG R19=> ThInit, db_connect ( DB-Connect 000256) [thxxhead.c 1411]

M in_ThErrHandle: 1

M *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c 10169]

-

---

There is no "C Nls CharacterSet..." line, the problem must be something regarding NLS charactersets, non-unicode/unicode issues...

But we don't know how to solve the problem.

Any idea?

Thanks again,

Jon

[markus_doehr2 · Accepted solution]

> parameter.

> C assuming using instant client with unspecified

> location.

> C Oracle Client Version: '10.2.0.1.0'

> C Client NLS settings: AMERICAN_AMERICA.WE8DEC

> C Logon as OPS$-user to get SAPBWT's password

> C Connecting as /@BWK on connection 0 (nls_hdl 0)

> ... (dbsl 700 110706)

> C Nls CharacterSet NationalCharSet

> C EnvHp ErrHp ErrHpBatch

> 1

You are still using the non supported Oracle instant client 10.2.0.1 - please update that one and try again.

--

Markus

[jonlarruzea · Accepted solution]

Hi Markus,

Thanks again for your help. We did already update the Oracle client but we continue with the same error:

-

---

M calling db_connect ...

C dbs/ora/array_buf_size = 650000

C CLIENT_ORACLE_HOME is not set as environment variable or

C DIR_CLIENT_ORAHOME is not set as profile parameter.

C assuming using instant client with unspecified location.

C Oracle Client Version: '10.2.0.2.0'

C *** ERROR => OCI-call 'OCIEnvCreate' failed: rc = -1

[dboci.c 2159]

C *** ERROR => OCI-call 'OCIErrorGet' failed: rc = -2

[dboci.c 1986]

B ***LOG BY2=> sql error -1 performing CON [dbsh#2 @ 1204] [dbsh 1204 ]

B ***LOG BY0=> Cannot get Oracle error text. [dbsh#2 @ 1204] [dbsh 1204 ]

B ***LOG BY2=> sql error -1 performing CON [dblink#3 @ 431] [dblink 0431 ]

B ***LOG BY0=> Cannot get Oracle error text. [dblink#3 @ 431] [dblink 0431 ]

M ***LOG R19=> ThInit, db_connect ( DB-Connect 000256) [thxxhead.c 1411]

M in_ThErrHandle: 1

M *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c 10169]

-

---

As already explained before, we don't see any entry in work process log to check NLS settings:

"C Client NLS settings: AMERICAN_AMERICA.WE8DEC"

We think that the problem must be relationated with this issue but we are not sure...

Thanks again,

Jon

[markus_doehr2 · Accepted solution]

The problem you may see is the fact, that you are logged on with <sid>adm, the SAP system runs under SAPService<SID>. So the environment you see now is not necessarily the environment SAPService<SID> has.

Check

556232 - Environment settings for R/3/Oracle on Windows

--

Markus

[markus_doehr2 · Accepted solution]

Another problem I could think of could be the fact, that the AddIn installation put a Unicode Kernel in your \usr\sap\<SID>\SYS\exe\run

To verify open a cmd.exe as user <sid>adm and execute

disp+work -V | more

and check if the kernel is a Unicode kernel.

--

Markus

[jonlarruzea · Accepted solution]

Hi Markus,

The problem is solved. You were right the problem was the Oracle environment variables. The Java add-in installation had deleted some Oracle environment variables from the regedit, after recreating it everything is OK.

Based on your recommendations and on the problems we had with the BI Java add-in installation over the BI Abap Oracle (non-unicode) instance, we will discard this option. We will make a BI Java installation in a new Oracle instance appart from the BI Abap instance (MCOD installation).

Could you please confirm us that this is the best solution from your point of view?

Thanks again Markus for your great help!!!!

Kind regards,

Jon

[markus_doehr2 · Accepted solution]

You´re welcome

The problem you face is not the problem, that you can´t "mix" UC and non-UC but the fact, that your BI system is a non-unicode system. Putting the J2EE in separately won´t solve the problem of the backend (in this case the BI) still being non-unicode and thus being not/no more supported.

On the coming frontend (the portal) you can enter whatever you want because Java is Unicode only, the backend however, may or may not be able to deal with the data you entered.

For a test/training system this can be ok - but for production I would seriously consider migrating to Unicode, also because all successor versions of SAP products will be released Unicode-only.

I know, this is a big issue, especially if you have an ERP/R/3 also, that is not yet Unicode. Additionally there come other technical things into place, such as the higher memory needs and thus the need for 64bit platforms, which you do not yet have (according to what information I have out of this thread here).

--

Markus

[jonlarruzea · Accepted solution]

Hi Markus,

We agree with your comments regarding the possible problems with a non-unicode BI Abap. As you say all our actual backends (R3, BW, SRM etc.) are non-unicode, that is the reason for which we decided to upgrade our SAP systems in a first phase and then migrate them to unicode.

We will evaluate our new BI 7.0 system in the integration server and schedule a unicode migration if it is necessary.

Thanks again for your great help and kind regards,

Jon

[markus_doehr2]

This combination is unsupported, read

note 975768 - Deprecation of Java features with non-Unicode Backend

You will need to convert your BI 7.0 first to Unicode.

(this is not the solution for your error but it doesn´t make sense to give suggestions for an unsupported combination)

--

Markus