cancel
Showing results for 
Search instead for 
Did you mean: 

ORA 04031 and OSIServer Attach failed at the time of installation

Former Member
0 Kudos

Hello to every one,

i am installing ecc 6.o with win 2003 having 2gb ram.set virtual memory up to 5000-6050.

every thing is ok....

but in ABAP IMPORT after ( completing 22 job successfully ) phase...i got the error that is related to SHARED_POOL_SIZE

error was

ORA: 00604 error occurred at recursive SQL level 1

ORA -04031 unable to alocate 4105 bytes of shared memory.

then i checked in initSID.ORA file SHARED_POOL_SIZE is quit low nearby 144 mb

then i increase it to 512 mb.and restart the server and again start the installation...

SHARED_POOL _SIZE upto 536870912 meann 512 mb

when i am checking though SQLPLUS as sysdba

it is showing me 512 m

that's ok....

but after restarting when i contuni the installation it is showing me error ..

in the same way that SAPAPPL2_3

SAPAPPL2_2

SAPAPPL0_2

are failed when i check the log file then it is showing....me

OCI-CALL OCIServerAttach failed: rc = 12541

connect failed with sql error '12541'

DbslErrorMsg rc=99so what will be that error

please suggest

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

thanks

Former Member
0 Kudos

Hi Anuj,

Did you check your listener status?

Just check whether listener is up or not? If not start listener and proceed.

Regards

Nick Loy

former_member603052
Contributor
0 Kudos

Hi Anuj,

The shared pool size in not sufficient.

You restart the system and continue the same old installation from where it stopped

The buffers will be refreshed at restart.

Error '12541' -


Also check the listener is up and running

Regards,

Kalyan

Former Member
0 Kudos

when i am trying connect to SQPLUS through cmd level

system/ as sysdba

then it says

SQL>

connect to ideal database.....

and if i

SQL>startup nomount

then

it starts

but

when i am trying installation again from where it stoped then it is showing same error

OCU-CALL: OCIServerAttach failed rc =12541

suggest

former_member603052
Contributor
0 Kudos

Hi Anuj,

First Check the listener is up and running

From command prompt run lsnrctl stat

Connected to idle instance means the database is not open yet.

Open the database with command startup open

Regards,

Kalyan