*** ERROR => Get of the precompiler version failed : sqlcode=-888

[Former Member]

Hello!

After moving a ERP 2004 system to a SLES9 EMT64 server (originally installed on 32 BIT SLES8) the MaxDB starts ok on the SLES9, but when starting SAP the processes terminates with the following error message:

• ERROR => Get of the precompiler version failed : sqlcode=-888

(Could not load libpcr (7.4.3-.))

We think this is caused by the fact the system was origianlly installed

on 32bit SLES8. We have also done som research, but cant find any short

term solution.

The version of MaxDB is 7.5.00.32

Best regards,

Fredrik

[Former Member · Accepted solution]

Hello,

did you have reinstalled the clientsoftware new or just copied?

Please try to display the registered installations with the registration tool irconf located in <indep_prog>/runtime/7403/bin. The option -s shows you the installed version.

Regards,

Burkhard

[Former Member · Accepted solution]

Hello Burkhard,

/sapdb is actually the pfysical volume (file system) that was orginally mounted (netapp/nfs) on the SLES8 box. (so we didn't copy anything)

srv004:sidadm 51> /sapdb/programs/bin/irconf -s

/sapdb/programs/runtime/7403 -> 7.4.3.0

srv004:sidadm 52> /sapdb/programs/bin/irconf -a

/sapdb/programs/runtime/7403 -> 7.4.3.0 from user registration

/sapdb/programs/runtime/7500 -> 7.5.0.0 from global registration

/sapdb/programs/runtime/7403 -> 7.4.3.0 from global registration

/sapdb/programs/runtime/7300 -> 7.3.0.0 from old registration

/sapdb/programs/runtime/7301 -> 7.3.1.0 from old registration

srv004:sidadm 53>

//Fredrik

[Former Member · Accepted solution]

Hi,

what does the ldrdiag.pct says. You can activate it with 'irconf -l on'

Burkhard

[Former Member · Accepted solution]

srv004:sidadm 52> irconf -l

Writing of loader trace /home_sap/sidadm/.sdb/ldrdiag.pct disabled.

srv004:sidadm 53> irconf -l on

Writing of loader trace /home_sap/sidadm/.sdb/ldrdiag.pct enabled.

What is supposed to be logged into that file? Nothing in there despite restart of application.

srv004:/sapdb/data/config # ll /home_sap/sidadm/.sdb/ldrdiag.pct

/bin/ls: /home_sap/sidadm/.sdb/ldrdiag.pct: No such file or directory

//Fredrik

[Former Member · Accepted solution]

The hope was to see more about attaching the client runtime (libpcr).

In the ldrdiag.pct will be logged the startup phase and the versioning

system to find the highest matching runtime.

Burkhard

[former_member229109 · Accepted solution]

Hello Fredrik,

As SAP customer you reported this issue in the OSS message 832240/2007. Correct?

Thank you and best regards, Natalia Khlopina

[Former Member · Accepted solution]

Hello Natalia,

Yes, that's correct!

I have got two options from SAP support, the first one is to look at the LD_ASSUME_KERNEL=2.4.1 (for sidadm, sqdsid, sdb) , which I actually tested already last night, but unfortunatly that does not seem to work.

Do you have any experience about this parameter? It would be a very smooth workaround for the moment.

The other options is to migrate maxdb to a 64bit kernel of version 7.5.0.0.44 or higher build. That would be a more tricky solution in a first glance.

Regards,

Fredrik

[former_member229109 · Accepted solution]

Hello Fredrik,

To avoid any misunderstanding & double work of my colleagues please

keep the message 832240/2007 updated, if you have further questions/problems.

-> First, SAP does not support the use of the MaxDB 32 Bit Version on the 64 Bit

Operation system.

-> Please review the note :: 822239 FAQ: MaxDB Interface

< 8. Where does irconf receive the information from? >

You have the SAP kernel 640.

-> As of MaxDB 7.5 the Precompiler Registration file for Precompiler Version

7.5 is located under /sapdb/data/config/Runtimes.ini, the old versions (7.2.5 - 7.4.3)

registered with the related executable from /sapdb/programs/runtime/<versions>/bin/irconf

The register information created in the file /usr/spool/sql/ini/SAP_DBTech.ini

< It has to be done by database installation & upgrade tools.

Problem you had may be occurred when you copy the database software

& then try to register it manually. Not recommended. >

-> And in your case the SAP kernel 640 was looking register in the

/usr/spool/sql/ini/SAP_DBTech.ini & was not able to find it.

-> The problem was fixed after the following command was executed:

/sapdb/programs/runtime/7403/bin/irconf -i -p /sapdb/programs/runtime/7403

Thank you and best regards, Natalia Khlopina

[Former Member · Accepted solution]

Hello Natalia!

I have updated the SAP message, just minutes ago.

The system is up and running, and put into production.

(We had to deal with network stuff a couple of hours this morning, in order to get the system available for the customer).

We are very satisfied with the help you provided last night, and hopefully we can share that for the forum users! I will do some more analysis, and consider a plan for this system on the long run. (if we need to migare to 64bit Maxdb anyway for instance?).

Best regards,

Fredrik

[markus_doehr2]

How did you "move" the system? Homogeneous system copy? Do you use the 64bit version of the database software?

--

Markus

[Former Member]

Because we use network attach storage, we just mounted the original filesystems (/sapdb, /sapdata...../usr/sap.../home/sdq<sid>...) to the new SLES9 EMT64 server, and

of course did some preparations in order to run SAP. Including the /etc/services, hosts and so on....

But pretty much switching over /sapdb that was orgininally installed on the SLES8 32 bit box.

So we still are on 32bit MaxDB (and 32bit SAP) on this SLES9 box.

(that shall be backward compatible).

//Fredrik