cancel
Showing results for 
Search instead for 
Did you mean: 

internal error in export/import buffer during startup

david_batho4
Explorer
0 Kudos

Hi folks,

My server was rebooted and now the sap system won't start.

Windows 2003, SQL Server 2005. Has been working fine for a long time.

I've tried restarting everything and changing memory parameters - seams like there is same available memory and pagefile as before. No other errors in the event logs worth noting.

I get these errors in the WP traces...

B dbtbxbuf: Buffer TABL (addr: 00000000230E0160, size: 30000000, end: 0000000024D7C4E0)

B dbtbxbuf: Buffer TABLP (addr: 0000000024D80160, size: 4096000, end: 0000000025168160)

B dbexpbuf[EXP_SHB]: Aquired semaphore 35 in db_exp_init(EXP_INIT)

B Layout of EIBUF buffer shared memory:

B 0: 1 * 4 = 4

B 1: 1 * 352 = 352

B 2: 25 * 40 = 1000

B 3: 40009 * 40 = 1600360

B 4: 20000 * 160 = 3200000

B 5: 40009 * 8 = 320072

B 6: 1 * 200 = 200

B 7: 65 * 8 = 520

B ***LOG BYE=> invalid interface parameter buf_area [dbexpbuf#2 @ 9256] [dbexpbuf9256 ]

B dbexpbuf[EXP_SHB]: semaphore 35 released in db_exp_init

B ***LOG BBF=> internal error in export/import buffer: object buf init fail [dbexpbuf#2 @ 2729] [dbexpbuf2729 ]

B dbexpbuf: return code (sap_rc): 16

B Buffer 0 will not be available

B Unexpected returncode from db_exp_init(EXP_ATP) : 16

B db_objinit failed

M *** ERROR => ThCallHooks: event handler db_init for event CREATE_SHM failed [thxxtool3.c 261]

M *** ERROR => ThIPCInit: hook failed [thxxhead.c 2118]

M ***LOG R19=> ThInit, ThIPCInit ( TSKH-IPC-000001) [thxxhead.c 1545]

M in_ThErrHandle: 1

M *** ERROR => ThInit: ThIPCInit (step 1, th_errno 17, action 3, level 1) [thxxhead.c 10589]

M

M Info for wp 0

M

M pid = 4292

M severity = 0

I would appreciate assistance is troubleshooting this further.

Kind regards,

Dave

Accepted Solutions (0)

Answers (2)

Answers (2)

david_batho4
Explorer
0 Kudos

The instance is now able to be started.

The parameter rsdb/obj/max_objects is now adjusted from 20000 (was adjusted by Sap upgrade tool during 701 ugprade) to 2000 (SAP default) and the work processes are then able to obtain the required shared memory.

Former Member
0 Kudos

Seems the SAP system is unable to allocate/create shared memory that is needed.

Can you do a "cleanipc remove <instance #>" and then try starting the SAP system again.

- Regards, Dibya

david_batho4
Explorer
0 Kudos

Thanks Dibya,

I understand that the cleanipc command for cleaning up shared memory applies to unix only.

We are on Windows as I've mentioned.

I've read that there may be something using the saposcol -d but I've rebooted the server a few times so this should clean up any shared memory on windows.

Kind regards,

Dave