Database instance installation

[Former Member]

Hello,

We are receiving the following error while performing the Database instance installation, error occurs in the post processing phase. We have detached, and reattached successfully.

Install CD’s were copied to local disk prior to running install.

BW database instance installation (post processing) error –

MSC-01002 Couldn't create package table, no packages found in: Z:\Data Files\BWP\data

ERROR 2006-09-01 13:07:32

FJS-00012 Error when executing script.

Does anyone have any ideas on what can be checked or any advice on how to get this resolved?

Thanks,

Nick

Message was edited by: Nick Bertz

[Former Member · Accepted solution]

The install user need special rights to write to the DB. don't know what they are off the top of my head, re read that part of the instructions.

[KITSA]

MSC-01002 : Could not create package table, no packages found in: …

I solved it, but I tried too many things at once so I don't know what exactly did it, so I am going to list them all.

The error occurred when I tried to create the Database Instance for 470x200 for Oracle on Win2003 I386, immediately after the step when to define the location of the export CD’s and the R3Load sequence.

1. Wrong choice of dir name. I copied the export CD’s on a local root directory called “C:sapcds”. I renamed it to “«G:export»”, in combination with the next step.

2. Very Slow I/O. I had copied the export CD’s on a the local disk C:. I copied them to the Storage Array Drive G:.

3. I removed all attributes from the root dir «G:export» and their sub-directories (cmd > attrib -R -A -S -H «G:export» /S /D )

4. I changed the Access Security Settings on «G:export» to include the Local and Domain Administrator with Full Access, as well as the “sidadm” and “SAPServiceSID” users.

5. In all the local server groups of ORA*, I added the “sidadm” and “SAPServiceSID” users again, as well as the local and domain Administrator.

6. In all the local server groups of SAP*, I added the “sidadm” and “SAPServiceSID” users again, as well as the local and domain Administrator.

7. Since I had a Windows Domain Installation, I made sure the “sidadm” and “SAPServiceSID” users are in the Administrators Group, the Domain Admin Group and the Domain User Group.

I know that some of the steps above seem stupid and no way that that was the source of the problem (eg. step 1 and 2, but I had no time to check them out, so please indulge me.

After all that, and a reboot of course, the installation proceeded as planed with no further problems.

Athanassios Kitselis

d.d.synergy Hellas