Symptom
Migration hung at phase "Create database schema" when you install target system via SWPM, and there will no further update in sapinst_dev.log besides following:
********************
TRACE 2014-09-12 18:47:13.674
NWUsers.getAccountData(): {
role:SAPSIDDB
type:USER
systems:db
id:
name:SAPSR3DB
comment:PSAPTEMP
home:
shell:
privileges:
exists:false
client:
host:undefined
instancenumber:undefined
locked:false
chownHomeDir:true
password:XXXXXX
groups:
}
TRACE 2014-09-12 18:47:13.674
OraCom(SchemaJava: SAPSR3DB)
TRACE 2014-09-12 18:47:13.678
NW(createSchemaJava: SAPSR3DB SAP PSAPTEMP)
TRACE 2014-09-12 18:47:13.678
OraSqlScript3.execute: Going to execute 'ORA_CREATE_DBUSR.SQL'
TRACE 2014-09-12 18:47:13.679
_objectContainsFunction: found function checkValid
TRACE 2014-09-12 18:47:13.688 [iaxohsqlx.hpp:1126]
COraSQLScriptExec<LoggingStrategy>::executeScript()
Temporary SQL script file: <ora_scr_tmp.sql>
TRACE 2014-09-12 18:47:13.693 [syuxcuser.cpp:701]
PSyGroupImpl CSyUserImpl::getPrimaryGroup()const
lib=syslib module=syslib
account user="orafc1" uid="2002" exists with parameter gid="2002"
TRACE 2014-09-12 18:47:13.697 [syuxcuser.cpp:701]
PSyGroupImpl CSyUserImpl::getPrimaryGroup()const
lib=syslib module=syslib
account user="orafc1" uid="2002" exists with parameter gid="2002"
TRACE 2014-09-12 18:47:13.701 [syuxcuser.cpp:701]
PSyGroupImpl CSyUserImpl::getPrimaryGroup()const
lib=syslib module=syslib
account user="orafc1" uid="2002" exists with parameter gid="2002"
TRACE 2014-09-12 18:47:13.705 [syuxcuser.cpp:701]
PSyGroupImpl CSyUserImpl::getPrimaryGroup()const
lib=syslib module=syslib
account user="orafc1" uid="2002" exists with parameter gid="2002"
TRACE 2014-09-12 18:47:13.727 [syuxctask.cpp:276]
CChildApplicationImpl::doStart() lib=syslib module=syslib
A child process has been started. Pid = 171225
********************
And, you will see there is no further update in ora_sql_results.log after following:
********************
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Connected.
old 4: :sSchema := upper('&&1');
new 4: :sSchema := upper('SAPSR3DB');
old 5: :passwd := '&&2';
new 5: :passwd := 'SAP';
old 6: :defTablespace := upper('&&3');
new 6: :defTablespace := upper('PSAPTEMP');
********************
Then, by checking the ORA_CREATE_DBUSR.SQL script, you will see the script requires 4 parameters:
********************
begin
:sSchema := upper('&&1');
:passwd := '&&2';
:defTablespace := upper('&&3');
:tempTablespace := upper('&&4');
end;
********************
Read more...
Keywords
ORA_CREATE_DBUSR.SQL, Create schema, system copy/migration , KBA , BC-DB-ORA , Oracle , BC-INS-MIG , OS/DB Migrations with SWPM and DB refresh , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview