[Thr 2960]
************************************************************* *** ERROR => Java VM initialization failed.
*** Please see SAP Note 943602 , section 'Java VM initialization issues' *** for additional information and trouble shooting.
**********************************************************************
[Thr 2960] JLaunchCloseProgram: good bye (exitcode = -1)
Solution:
1. Apply SAP note 831812
2. Start the GUI ConfigTool and remove the XJ9 parameter from the bootstrap settings for the instance, dispatcher and server. 3. Edit the file $(DIR_INSTANCE)/j2ee/cluster/instance.properties and
remove the XJ9 setting from the bootstrap*.JavaParameters properties as well.
-------------------------
Object Checker reports unloaded packages for split tables Symptom:
After the data import SAPinst displays a popup with the warning that not loaded packages have been found by the Object Checker. The Object Checker's logfile contains error messages like:
TSK file '.TSK' not found for package 'TABLE'. ...
Not loaded packages are saved in 'invalid_objects.txt' file.
Solution:
Warnings referring to tables split by R3ta can be ignored. Currently the Object Checker cannot handle such packages correctly.
-------------------------
Table splitting restrictions: LRAW and RAW fields
RAW or LRAW field cannot be used within the where condition. If you want to split a table, which contains RAW or LRAW fields as part of the table's
key, use an R3ta with patch level >=4 (compile date newer than
10/JULY/2007). This R3ta will ignore RAW and LRAW fields when creating where conditions.
-------------------------
Using virtual hosts for central and/or DB instances SYMPTOM:
You are using virtual host names for your central instance and/or the database instance (e.g. in a HA environment). Although SAPinst finishes successfully, some export steps are not being performed. SOLUTION:
Start the export with the property SAPINST_USE_HOSTNAME=
If you run a central system with different host names in the profiles, handle the export as a distributed export, calling SAPinst with parameter SAPINST_USE_HOSTNAME. Perform the export of the database instance on the DB server, calling SAPinst with SAPINST_USE_HOSTNAME=
-------------------------
Java: Follow-Up Activity: Installing the License Key
BEFORE installing the license key, make sure to apply SAP Note 831812.
-------------------------
Table splitting for tables starting with '/' When trying to process tables starting with '/', the step 'R3ta' will abort when trying to create the R3ta log and WHR files. To leverage processing of tables starting with '/', a correction in two functions in the control.xml file is required:
4. Start the SAPinst service 'Table Splitting Preparation'. When you are asked for the first input, interrupt the installation. 5. Edit the file control.xml in your installation directory (for the export). 6. Search for string 'function checkWhrCondOk'. Within the function, perform the following changes:
a) Add the following line as first line of the function body: var sTabName = sTable.replace(/\\//g, \
b) Replace 'sTable' by 'sTabName' in the declaration of variable fWhrFile: old: var fWhrFile =
oFileMgt.getNode(sWhrDir+\new: var fWhrFile =
oFileMgt.getNode(sWhrDir+\
c) Search for string 'function startR3ta'. Within the function, perform the following changes:
d) Add the following line as first line of the function body: var sTabName = sTable.replace(/\\//g, \
e) Replace 'sTable' by 'sTabName' in the declaration of aR3taArgs[1], aR3taArgs[6] and aR3taArgs[8]: old: aR3taArgs[1] = \new: aR3taArgs[1] = \old: aR3taArgs[6] = \new: aR3taArgs[6] = \old: aR3taArgs[8] = \new: aR3taArgs[8] = \
7. Restart the installation and choose 'Continue with old
installation'. Now the installation will run with the control.xml file which you have adapted in the installation directory.
-------------------------
Table splitting: '/' characters in column names When the column names used inside the R3ta WHR files contain '/' characters, and these column names are not masked with double quotes, the R3load export will abort.
Use an R3ta with patch level >=3 (compile date newer than 24/MAY/2007). This R3ta will quote the column names correctly.
-------------------------
Copying an upgraded system: client 001 missing
If you want to copy an upgraded system make sure that client 001 exists. If this is not the case, proceed as follows:
Before logging on to the system, adjust parameter login/system_client in file DEFAULT.PFL according to the definition on the source system.
-------------------------
SQL files in export directory need to have read access
Make sure that the SQL files in the export directory have read access (for example, 644).
-------------------------
ABAP/Table Splitting: wrong format of input file
Ensure that the file with the list of tables to be split does not contain any empty lines. Otherwise SAPinst will abort with a message like: Reading of table split file failed. Line \expected format tablename%numsplits.
-------------------------
ABAP: The job RUTSMJOB returns an error in the system after the import: \definitions in the ABAP dictionary and database are not consistent\Solution:
Apply SAP Note 999910.
--------------------------
When running the service 'Table Splitting Preparation' the step 'R3ta' of component 'TableSplitter' will fail with the following error message in file sapinst_dev.log:
... Call to R3ta failed for table . ...
In addition you will find the following error message in file sapinst_syslib_priv.log: Error in execvpS(R3ta errno: 2, error text: A file or directory in the path name does not exist.
Solution:
Make sure that you have an R3ta in the kernel directory. In contrast to the system copy guide the installation master DVD does not contain an R3ta executable and a R3ta_hints.txt file. Download the R3ta*.SAR archive from the SAP SMP, extract it to the installation directory for the table splitting preparations and move the R3ta executable to the kernel directory.
-------------------------- 19/DEC/06>-------------------------- Follow-Up Activity: After the system copy has finished, you have to perform the following step manually: If the data is stored in the file system, job logs, batch input logs, and spool jobs are stored in the directory DIR_GLOBAL. The files can be found in the following sub-directories: ? ? ? xxxBDCLG xxxJOBLG xxxSPOOL You have to copy these files manually from the source to the target system for every client. ------------------------- Java Export: error during export of table CAF_GP_R3USRMPGCFG or CAF_GP_IF_CONTEXT Symptom: The export aborts with one of the following error message in jload. java.log: SEVERE: DB Error during export of CAF_GP_R3USRMPGCFG ... SEVERE: Message: ORA-00942: table or view does not exist or SEVERE: DB Error during export of CAF_GP_IF_CONTEXT ... SEVERE: Message: ORA-00942: table or view does not exist Solution: Delete the entry for table CAF_GP_R3USRMPGCFG or for table CAF_GP_IF_CONTEXT from the dictionary of the Java engine. Connect to the database as your database schema user and execute the following statement on database level: DELETE FROM BC_DDDBTABLERT WHERE NAME = 'CAF_GP_R3USRMPGCFG'; or DELETE FROM BC_DDDBTABLERT WHERE NAME = 'CAF_GP_IF_CONTEXT'; Disconnect from the database and repeat the export step with SAPinst. ------------------------