Oracle 11g OUI error - INS-07009 Unable to load bean store

During installation of Oracle, encountered the below error.

INS-07009 Unable to load bean store

This is caused due to Environmental variable PS1. The value of PS1 should be ora < DBSID >. But in this case the value of this parameter was showing up in next line when I gave the command env.


The problem solved executing export PS1="oraSID >;". This means, correcting either environmental variable file or manually adding it in the session where Oracle OUI is being run.

setenv PS1 oraxyz>


PS1=oraxyz>;export PS1

Problems Installing or System Copy Import to Oracle 11g

Issue - Deprecated Parameters
When you run sapinst and a database is created, it will create the initial initSID.ora profile with the parameter remote_os_authent = true.  At some point in the installation, sapinst restarts Oracle, which then returns an error like

Error message: ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance

When you see this, leave the sapinst message up, but edit initSID.ora and remove the line remove_os_authent = true.  Restart Oracle with "shutdown immediate" and "startup nomount" and click "retry" in sapinst.  This will cause its own problems later on, so you will need to add it back and restart Oracle once the database has been created.

Be sure that there are no other "deprecated parameter" messages after you do this.  Any such message will cause sapinst to stop dead in its tracks.  Other deprecated parameters include "user_dump_dest" and "background_dump_dest".

ORA-01017: invalid username/password; logon denied

SAPINST error while DB installation on Oracle 11g

New Password Case Sensitivity Feature
With 11g installations, you will encounter problems if you entered a lowercase database password in your sapinst parameter screens.  The problem is that passwords now have case-sensitivity enforced in 11g.  You may encounter a message like:

ORA-01017: invalid username/password; logon denied

While you are editing initSID.ora to solve , set the following parameter and restart Oracle:


ERROR- unknown template variable compress in sapinst

Error: During Heterogeneous system copy using SAPINST – Import phase got below error.

(TPL) ERROR: unknown template variable "compress"

Solution: Get the latest R3load executable to resolve the issue

ORA-12899: value too large for column

Error in SAP system:

Database error text........: "ORA-12899: value too large for column
 ""."KAPOL"."VARDATA" (actual: 72, maximum: 36)"
Internal call code.........: "[RSQL/INSR/A016 ]"
Please check the entries in the system log (Transaction SM21).

Solution is in SAP Note 686357.

Executed report RATPONTC as per note 686357.

Sticky bit permissions for SAPOSCOL

Sticky bit permissions for saposcol on Unix platforms
chown root:sapsys saposcol
chmod 4750 saposcol

sapinst system copy error on oracle 11g database

During System Copy using ECC 6.0 SR3 Installation master on oracle database version 11g you may encounter another problem with sapinst if it tries to execute the command execute DBMS_SCHEDULER.DISABLE('GATHER_STATS_JOB'); This job does not exist in 11g and your installation will stop with the message:

DIAGNOSIS: Error message: ORA-27476: "SYS.GATHER_STATS_JOB" does not exist

You need to edit the control.xml file in your installation directory and comment out the GATHER_STATS_JOB disabling command. Just put "--" before the word "execute" so your line looks like this:

stream.putLine("--execute DBMS_SCHEDULER.DISABLE('GATHER_STATS_JOB');");

This shouldn't be necessary, but do it anyway: Edit the file dbms_scheduler.sql in your installation directory and comment out the line (created as per control.xml) so it looks like this


Stop sapinst! Restart sapinst, chosing exactly the same options as before, and choose "continue old installation". Your installation should run through now.

SAPinst Error during installation "Resource temporarily unavailable"

Error: EsStdUnamFileMapInit: Info: mmap() failed. errno = 11(Resource temporarily unavailable)

Solution: Remove parameter es/implementation=std from Instance profile and restart SAP.
Then re-run SAPinst.

Also check SAP Note 941735 - SAP memory management for 64-bit Unix Systems.

Below command can be very useful as well.

/usr/sap//SYS/exe/run/memlimits | more