Error by Installing Sol. Manager 4.0 with Oracle on Windows 2003 x64

[Former Member]

Hello,

By installing Sol. Manager 4.0 with Oracle on Windows 2003 x64 I get errors by the step Import ABAP. Only 4 objects of 18 are imported correctly.

Logs:

import_monitor.java.log:

java version "1.4.2_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_12-b03, mixed mode)
Import Monitor jobs: running 1, waiting 13, completed 4, failed 0, total 18.
Import Monitor jobs: running 2, waiting 12, completed 4, failed 0, total 18.
Import Monitor jobs: running 3, waiting 11, completed 4, failed 0, total 18.
Loading of 'SAPSSRC' import package: ERROR
Import Monitor jobs: running 2, waiting 11, completed 4, failed 1, total 18.
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 1, waiting 11, completed 4, failed 2, total 18.
Loading of 'SAPPOOL' import package: ERROR
Import Monitor jobs: running 0, waiting 11, completed 4, failed 3, total 18.
[...]

SAPAPPL2.log:

[...]K:usrsapSM1SYSexeucNTAMD64R3load.exe -i SAPAPPL2.cmd -dbcodepage 4103 -l SAPAPPL2.log -stop_on_error 

DbSl Trace: OCI-call 'OCIServerAttach' failed: rc = 12518

DbSl Trace: CONNECT failed with sql error '12518'

DbSl Trace: OCI-call 'OCIServerAttach' failed: rc = 12518

DbSl Trace: CONNECT failed with sql error '12518'

(DB) ERROR: db_connect rc = 256
DbSl Trace: OCI-call 'OCIServerAttach' failed: rc = 12518

DbSl Trace: CONNECT failed with sql error '12518'

DbSl Trace: OCI-call 'OCIServerAttach' failed: rc = 12518

DbSl Trace: CONNECT failed with sql error '12518'

(DB) ERROR: DbSlErrorMsg rc = 99

K:usrsapSM1SYSexeucNTAMD64R3load.exe: job finished with 1 error(s)
K:usrsapSM1SYSexeucNTAMD64R3load.exe: END OF LOG: 20060609111437
[...]

Have someone an idea?

Thank you.

Regards,

Tommaso

[Former Member · Accepted solution]

What's the Oracle version?

Heard Windows 2003 is not compatible with Oracle8i.

Wonder whether this can be a problem in ur case..

[Former Member · Accepted solution]

I use Oracle 10g.

Regards,

Tommaso

[Former Member · Accepted solution]

Below is the output of !oerr ora 12518.

12518, 00000, "TNS:listener could not hand off client connection"

// *Cause: The process of handing off a client connection to another process

// failed.

// *Action: Turn on listener tracing and re-execute the operation. Verify

// that the listener and database instance are properly configured for

// direct handoff. If problem persists, call Oracle Support.

// *Comment: The problem can be worked around by configuring dispatcher(s)

// to specifically handle the desired presentation(s), and connecting

// directly to the dispatcher, bypassing the listener.

Not sure but I think the problem may be with your TNSlistner process..

[Former Member · Accepted solution]

Yes, but how and why?

tnsping work well, and (more important) 4 ABAP object have been imported correctly!

Regards,

Tommaso

[frank_tottleben]

Hello Tommaso,

I have the same problem sporadically (ORA-12518) during the startup of the J2EE engine of an XI 7.0 installation, which cause the engine to shutdown. The installation also runs on Oracle 10g and 2003 x64. Have you found a solution for this problem yet?

Best Regards,

Frank

[Former Member]

Hi Frank,

Then I opted for MaxDB, and the installation worked fine up to some problem with amount of the cache.

Now I would try to increase drastically the cache -> 25 GB

Regards,

Tommaso

[Former Member]

Hello Frank,

I am having currently the same problem with a XI3.0 (WAS 6.40).

Did you solve that problem?

Kind regards

David

[Former Member]

I also had this problem and I fixed it by increasing the value of Oracle parameters PROCESSES and SESSIONS as per note 830576. Make sure that the value of SESSIONS = 2 * PROCESSES.

Good luck,

Arwel.