Database Export with DB2 Version 9.5
Folks,
Has anybody ran a Database Export with ECC 6.0 or Solution Manager 7.0 etc ( AIX ) and DB2 Version 9.5 ?
When we have run it, it runs successfully ( so it says ) in seconds but obviously produces no dump file. My gut feel is that the Installation Master ( SR3 ) is prob okay it is some specific kernel components.
If anybody has any ideas it would be much appreciated.
Regards Russell
We got to the bottom of the problem it was associated with Virtual Hostnames. It wasn't picking up the Virtual Hostname and therefore didn't think there was anything to do. With the correct SAPINST_USE_HOSTNAME it connects in correctly and runs through.
Regards Russell
Similar Messages
-
Migrate Database- Export/Import
Hi,
I need to migrate an Oracle database 9i from Sun Solaris to Linux. The final target database version would be 11g.
Since this is a 9i database, I see that we have only option of export and database. We have around 15 schemas.
I have some queries related to it.
1. If I perform a export with full=y rows=y, Does it export Sys, System Schema objects also?
2. Can we perform export in Oracle 9i and use datapump import on targert 11g?
3. What is the ebst approach - a) to perform schema by schema export or b) to perform a full database export with exp / file=xxx.dmp log=xxxx.log full=y?
Since there is a database version different I dont want to touch sys, system schema objects.
Appreciate your thoughts.
Regards
Cherrish VaidiyanHi,
Let me try to answer some of these questions you queried for:
1. If I perform a export with full=y rows=y, Does it export Sys, System Schema objects also?Export won't export sys objects. For example, there are tables in sys, like obj$ that contain information for other metadata objects, like scott.emp, etc. This is not exported becuase when scott.emp is exported, the data from obj$ is essentially exported that way. When the dumpfile is imported and scott.emp is recreated, the data in sys.obj$ will be restored through the create table statement. As far as the SYSTEM schema is concerned, some objects are exported and some are not. There are tables in system that contain information about queues, jobs, etc. These will probably not make any sense on the target system so those types of tables are excluded from the export job. Other objects make sense to export/import so those are done. This is all figured out in the internals of export/import. Thre are other schemas that are not exproted. Some that I can think of are DMSYS, ORDSYS, etc. This would be for the same reason as SYS.
2. Can we perform export in Oracle 9i and use datapump import on targert 11g?No, the dumpfiles are formatted differently. If you use exp, then you must use imp. If you use expdp, then you must use impdp. You can do exp on 9i and imp on 11g with the dumfile that was created on 9i.
3. What is the ebst approach - a) to perform schema by schema export or b) to perform a full database export with exp / file=xxx.dmp log=xxxx.log full=y?This is case by case decision. It depends on what you want. If you want the complete database moved, then I would personally think that a full=y is what you would want to do. If you just did schema exports, then you would never export the tablespaces. This would mean that you would have to create the tablespaces on the source system before you ran imp. There are other objects that are not exported when a schema level export is performed that are exproted when a full is performed. This information can be seen in the utilities guide. Look to see what is exported when in user/schema mode vs full/database mode.
Since there is a database version different I dont want to touch sys, system schema objects.This is all done for you with the internal workings of exp/imp.
Dean
Edited by: Dean Gagne on Jul 29, 2009 8:38 AM -
Intergration with DB2 stored procedure
I am using Database adapter to integrate with DB2(version 8) to call a stored procedure,however i receive a message "The adapter configurationwizard doesnot support DB2 stored procedures."
I am using Jdeveloper 11g.Is there any work around or any other standard method for this.
Thanks in advance...Hi,
All explanation on Oracle note 1270851.1
Arik -
Database export stops with the following warnings.
Hello,
I am doing a Database Export/Import Activity. My DB is MS SQL server 2000 and SAP R/3 (4.6C SR2 , 4.6D kernel).
When i try to do a DB export with option split STR and EXT files, my export stops abruptly without giving any erorrs but with a whole list of warnings.
My splitting procedure is using SPLITSTR.PL perl script. I am not using the latest java based split.
For your reference i am pasting the whole DBEXPORT.log file.
(sorry its bit large,,, i hope you dont mind ) )
INFO 2008-03-29 14:36:21 CommandFileController SyFileVersionSave:736
Saving original content of file
C:\Users\prdadm\Install\DBEXPORT.R3S ...
INFO 2008-03-29 14:36:21 CommandFileController SyFileCopy:676
Copying source file C:\Users\prdadm\Install\DBEXPORT.R3S to
target file C:\Users\prdadm\Install\DBEXPORT.R3S.1 ...
INFO 2008-03-29 14:36:21 CommandFileController SyPermissionSet:2207
Changing permission for file C:\Users\prdadm\Install\DBEXPORT.R3S
from 777 to 666.
INFO 2008-03-29 14:36:21 Main
Preparation successfully completed.
INFO 2008-03-29 14:36:23 DBEXPORTINSTANCE_NT_IND DefValForKey_OS:0
R3Setup found the share 'SAPLOC' on drive E:.
INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:434
checking host name lookup for 'ELESAPTMP1'
INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:473
offical host name for 'ELESAPTMP1' is 'ELESAPTMP1.lntebg.com'.
INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:541
host 'ELESAPTMP1' has ip address '172.18.101.21'
INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:581
offical host name for '172.18.101.21' is 'ELESAPTMP1'.
INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:434
checking host name lookup for 'ELESAPTMP1'
INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:473
offical host name for 'ELESAPTMP1' is 'ELESAPTMP1.lntebg.com'.
INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:541
host 'ELESAPTMP1' has ip address '172.18.101.21'
INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:581
offical host name for '172.18.101.21' is 'ELESAPTMP1'.
INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:434
checking host name lookup for 'ELESAPTMP1'
INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:473
offical host name for 'ELESAPTMP1' is 'ELESAPTMP1.lntebg.com'.
INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:541
host 'ELESAPTMP1' has ip address '172.18.101.21'
INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:581
offical host name for '172.18.101.21' is 'ELESAPTMP1'.
INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:434
checking host name lookup for 'ELESAPTMP1'
INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:473
offical host name for 'ELESAPTMP1' is 'ELESAPTMP1.lntebg.com'.
INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:541
host 'ELESAPTMP1' has ip address '172.18.101.21'
INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:581
offical host name for '172.18.101.21' is 'ELESAPTMP1'.
INFO 2008-03-29 14:37:17 DBEXPSERVER_NT_IND InternalColdKeyCheck:0
The CD CDEXPORT1 will not be copied.
INFO 2008-03-29 14:37:36 DBEXPORTINSTANCE_NT_IND CheckValueForKey:0
The installation phase is starting now. Please look in the log
file for further information about current actions.
INFO 2008-03-29 14:37:36
Requesting Export Details
INFO 2008-03-29 14:37:36
Requesting Export Details
INFO 2008-03-29 14:37:36 DBEXPCOMMONDBENV_NT_MSS SyCoprocessCreate:931
Creating coprocess osql.exe ...
INFO 2008-03-29 14:37:36 DBEXPCOMMONDBENV_NT_MSS SyCoprocessExecute:171
The process osql.exe puts out:
INFO 2008-03-29 14:37:37 DBEXPCOMMONDBENV_NT_MSS GetDbVersion:0
Version String read from MS SQL Server: Microsoft SQL Server
2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38 Copyright
(c) 1988-2003 Microsoft Corporation Enterprise Edition on
Windows NT 5.2 (Build 3790: Service Pack 2)
INFO 2008-03-29 14:37:37 DBEXPCOMMONDBENV_NT_MSS GetDbVersion:0
Major Version read from MS SQL Server: 800
INFO 2008-03-29 14:37:37 DBEXPCOMMONDBENV_NT_MSS GetDbVersion:0
Minor Version read from MS SQL Server: 2039
INFO 2008-03-29 14:37:37 DBEXPCOMMONDBENV_NT_MSS SyCoprocessCreate:931
Creating coprocess osql.exe ...
INFO 2008-03-29 14:37:37 DBEXPCOMMONDBENV_NT_MSS SyCoprocessExecute:171
The process osql.exe puts out:
INFO 2008-03-29 14:37:37 DBEXPCOMMONDBENV_NT_MSS InternalInstallationDo:0
You have a correctly configured MS SQL Server with charset cp850
and sortorder bin_cp850!
INFO 2008-03-29 14:37:37 DBEXPCOMMONDBENV_NT_MSS InternalInstallationDo:0
ooo MSGERR Wrong type of Parameter: area:74, id:1, typeofParam:4, char:d
ooo MSGERR Dump of parameter with valid type:
ooo MSGWAR MsgAreaName:SY_AREA_RI_MSGL, MsgIdName:RI_MSGL_MIN_MAJORVERSION
ooo MSGERR --- SYLOGDATA:ParaNr: 1, Typ:4
ooo MSGERR --- SYLOGDATA:ParaNr: 2, Typ:1, long=0
ooo MSGERR --- SYLOGDATA:ParaNr: 3, Typ:1, long=0
ooo MSGERR --- SYLOGDATA:ParaNr: 4, Typ:1, long=0
ooo MSGERR --- SYLOGDATA:ParaNr: 5, Typ:1, long=0
ooo MSGERR --- SYLOGDATA:ParaNr: 6, Typ:1, long=0
ooo MSGERR --- SYLOGDATA:ParaNr: 7, Typ:1, long=0
ooo MSGERR --- SYLOGDATA:ParaNr: 8, Typ:1, long=0
ooo MSGERR --- SYLOGDATA:ParaNr: 9, Typ:1, long=0
ooo MSGERR --- SYLOGDATA:ParaNr:10, Typ:1, long=0
ooo MSGERR Wrong type of Parameter: area:74, id:1, typeofParam:4, char:d
ooo MSGERR Dump of parameter with valid type:
ooo MSGWAR MsgAreaName:SY_AREA_RI_MSGL, MsgIdName:RI_MSGL_MIN_MAJORVERSION
ooo MSGERR --- SYLOGDATA:ParaNr: 1, Typ:4
ooo MSGERR --- SYLOGDATA:ParaNr: 2, Typ:1, long=0
ooo MSGERR --- SYLOGDATA:ParaNr: 3, Typ:1, long=0
ooo MSGERR --- SYLOGDATA:ParaNr: 4, Typ:1, long=0
ooo MSGERR --- SYLOGDATA:ParaNr: 5, Typ:1, long=0
ooo MSGERR --- SYLOGDATA:ParaNr: 6, Typ:1, long=0
ooo MSGERR --- SYLOGDATA:ParaNr: 7, Typ:1, long=0
ooo MSGERR --- SYLOGDATA:ParaNr: 8, Typ:1, long=0
ooo MSGERR --- SYLOGDATA:ParaNr: 9, Typ:1, long=0
ooo MSGERR --- SYLOGDATA:ParaNr:10, Typ:1, long=0 Your actual major version of MS SQL Server is
INFO 2008-03-29 14:37:37
Requesting Export-Specific Parameters
INFO 2008-03-29 14:37:37
Testing the Database Connect
INFO 2008-03-29 14:37:37 DBDBSLTESTCONNECT_NT_IND InternalInstallationDo:0
See logfile dev_dbsl for further information.
INFO 2008-03-29 14:37:37 DBEXPSERVER_NT_IND InternalWarmKeyCheck:0
The CD CDEXPORT1 will not be copied.
INFO 2008-03-29 14:37:37
Requesting Information on CD-ROMs
INFO 2008-03-29 14:37:37
Creating the Export Directories
INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
Checking existence of directory F:\EXPORT~2\DB. If it does not
exist creating it with user NULL_POINTER, group NULL_POINTER and
permission 7 ...
INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
Changing permission for file F:\EXPORT~2\DB from 777 to 7.
INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
Checking existence of directory F:\EXPORT~2\DB\ORA. If it does
not exist creating it with user NULL_POINTER, group NULL_POINTER
and permission 7 ...
INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
Changing permission for file F:\EXPORT~2\DB\ORA from 777 to 7.
INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
Checking existence of directory F:\EXPORT~2\DB\INF. If it does
not exist creating it with user NULL_POINTER, group NULL_POINTER
and permission 7 ...
INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
Changing permission for file F:\EXPORT~2\DB\INF from 777 to 7.
INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
Checking existence of directory F:\EXPORT~2\DB\ADA. If it does
not exist creating it with user NULL_POINTER, group NULL_POINTER
and permission 7 ...
INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
Changing permission for file F:\EXPORT~2\DB\ADA from 777 to 7.
INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
Checking existence of directory F:\EXPORT~2\DB\MSS. If it does
not exist creating it with user NULL_POINTER, group NULL_POINTER
and permission 7 ...
INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
Changing permission for file F:\EXPORT~2\DB\MSS from 777 to 7.
INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
Checking existence of directory F:\EXPORT~2\DB\DB2. If it does
not exist creating it with user NULL_POINTER, group NULL_POINTER
and permission 7 ...
INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
Changing permission for file F:\EXPORT~2\DB\DB2 from 777 to 7.
INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
Checking existence of directory F:\EXPORT~2\DB\DB4. If it does
not exist creating it with user NULL_POINTER, group NULL_POINTER
and permission 7 ...
INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
Changing permission for file F:\EXPORT~2\DB\DB4 from 777 to 7.
INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
Checking existence of directory F:\EXPORT~2\DB\DB6. If it does
not exist creating it with user NULL_POINTER, group NULL_POINTER
and permission 7 ...
INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
Changing permission for file F:\EXPORT~2\DB\DB6 from 777 to 7.
INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
Checking existence of directory F:\EXPORT~2\DATA. If it does not
exist creating it with user NULL_POINTER, group NULL_POINTER and
permission 7 ...
INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
Changing permission for file F:\EXPORT~2\DATA from 777 to 7.
INFO 2008-03-29 14:37:37
Creating the R3load Control Files
INFO 2008-03-29 14:37:37 R3LDCTL_NT_IND R3ldctlDo:0
C:\Users\prdadm\Install\R3LDCTL.EXE -p C:\Users\prdadm\Install
INFO 2008-03-29 14:37:37 R3LDCTL_NT_IND SyCoprocessCreate:931
Creating coprocess C:\Users\prdadm\Install\R3LDCTL.EXE ...
INFO 2008-03-29 14:37:38 R3LDCTL_NT_IND R3ldctlDo:0
WARNING: no technical settings for table "A055" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "A056" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "A064" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "A065" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "AABLG" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "AANK" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "AANL" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "ALQRFCMON" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "ALQRFCMONA" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "ALQRFCMONO" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "ALQRFCMONQ" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "ANAR" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "ANEV" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "ANGA" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "ANLH" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "ANLV" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "ANLW" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "ANLX" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "APQD" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "APQI" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "ATAB" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "B015" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "B060" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "BGPROT" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "BKORA" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "BKORR" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "BPHIER" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "BSIW" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "BTCEVTJOB" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "BTCJSTAT" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "BTCOPTIONS" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "BTCSED" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "BTCSEV" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "BTCUEV" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "BUXPRA" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "BVOR" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "CATCU" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "CATDB" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "CATL" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "CATM" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "CBPL" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "CCCFINI" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "CD0BAS4VI" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "CD0BAS5VI" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "CD0MC5" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "CD0T200TAB" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "CD0T210TAB" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "CD0TBSH001" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "CDCLS" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "CE1S001" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "CE2S001" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "CE3S001" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "CE4S_CP_FLAG" in SAP
data dictionary - defaults used
WARNING: no technical settings for table "CF003" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "CF005" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "CFIS" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "CHGRP" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "CKHT" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "CKKS" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "CKKT" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "CKPP" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "CKPS" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "CKPT" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "CLRK" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "CLU4" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "CNTLREM" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "COKAA" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "COOI_PI" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "COSPP" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "CRHH" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "CRID" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "CRS_BLOCKS" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "CRVP" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "CSLT" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "CSSK" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "CVEP1" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "CVEP2" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "CVER1" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "CVER2" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "CVER3" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "CVER4" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "DD02ALL" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "DEBI" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "DELM" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "DLIX" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "DOKALTLANG" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "DOKCL" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "DOKID" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "DOKSH" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "DOKSI" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "DOSSH" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "DOSSI" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "DSYCR" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "DSYLI" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "DSYLT" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "DSYO1" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "DSYO2" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "DSYO3" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "DSYSX" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "DVERS" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "DVPOOL" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "DVPOOLTEXT" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "E070N" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "EANQ" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "EBSEG" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "EBUB" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "EDFIL" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "EDI30C" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "EDI40" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "EDIDOC" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "EDIE5" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "EDMAP" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "EIPA" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "EKAN" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "EKPB" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "EKUB" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "EPIDXB" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "EPIDXC" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "EREF" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "EREN" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "ERET" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "EST07" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "EST0B" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "EST0D" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "EST0F" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "EWUCUSA2" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "EWUCUSAK" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "FEBKEY" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "FINPL" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "FINS" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "FINV" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "FLAPP" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "FLEMP" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "FMCFSI" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "FMCOPI" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "FMGEBER" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "FOH01" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "FREF" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "GCLIENTS" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "GLOO1" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "GLOO2" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "GLPO1" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "GLPO2" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "GLPO3" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "GLS2CLUS" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "GLSO1" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "GLSO2" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "GLSO3" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "GLSP" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "GLT0" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "GLTO1" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "GLTO2" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "GLTO3" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "GLTP" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "GLTPC" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "GSBLCA" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "GWFEODE" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "HLPNA" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "HRARCENQ" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "HRMS_BIW_PPDELTA" in
SAP data dictionary - defaults used
WARNING: no technical settings for table "HRPMPROT" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "HRPMSIM" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "HRPY_RGDIR_TEMP" in SAP
data dictionary - defaults used
WARNING: no technical settings for table "IMPREDOC" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "INDX" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "INETX" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "INHB" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "IXDIT" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "IXTYP" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "IXTYT" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "JVT1" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "J_1AWITNR" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "J_1BCBTAXPROC" in SAP
data dictionary - defaults used
WARNING: no technical settings for table "J_1BITEMTYPES" in SAP
data dictionary - defaults used
WARNING: no technical settings for table "K002" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "KALK" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "KAPE" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "KAPOL" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "KBPOL" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "KCPOL" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "KDPOL" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "KEPOOL" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "KGPOL" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "KNAS" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "KNB5" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "KNC1" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "KNC3" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "KNMTK" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "KNOB" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "KNVA" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "KNVD" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "KNVI" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "KNVL" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "KNVS" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "KNVT" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "KOCLU" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "KONAIND" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "KOND" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "KONR" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "KOTD001" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "KOTE001" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "KOTE002" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "KOTE003" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "KOTE004" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "KOTE005" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "KOTG002" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "KOTG003" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "KRED" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "LDAN" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "LDKO" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "LFAS" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "LFB5" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "LFC1" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "LFC3" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "LISA" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "LISPLF" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "MASE" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "MAT1" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "MBAN" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "MBMP" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "MBPR" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "MBRK" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "MCEKS" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "MCLIB" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "MCLIO" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "MCLIP" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "MCLIT" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "MCVSRFP" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "MCY1" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "MEIK" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "MEIN" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "MEKK" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "MEOR" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "MHNDO" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "MHNKA" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "MKLK" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "MKUB" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "MLIB" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "MODSAP" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "MOFF" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "MPRP" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "MSAK" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "MSEGO1" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "MSET" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "MSOA" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "MSPOOL" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "MSTA" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "M_ADMC" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "M_ADRC" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "M_ADRP" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "M_AKTE" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "M_CF01" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "M_CKKA" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "M_CLFN" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "M_DARL" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "M_DGMI" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "M_HORD" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "M_IBEW" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "M_IFLM" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "M_IIMA" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "M_IRLM" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "M_J1BA" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "M_J1IA" in SAP data
dictionary - defaults used
WARNING: no technical settings for table "M_J1IB" in SAP data
dictionary - defaults usedHello,
The version of perl is correct.
Anayways i have solved the problem!
there was problem with the DBEXPORT.R3S file. i referred a SAP note for the same.(Installation of 4.6c on windows). In this check the section for post installation activity.
I hope this can be a input for other experts who may face such problem!!!
Regards,
Shridhar!!!! -
Service Registry error while starting after configuring with DB2 database
Hi
I installed WLS 9.1 / ALSR 2.1 on RedHat Linux 4 EL.And DB2 8.2 FP12
It was started fine with the default HSQL database, after changing the database to DB2 and restarted the server, I am getting the following errors
Any one know about this ..please help me. Seems it was alredy posted on forums.bea.com but those threads are not accessioble now.Appriciate any quick response
error log - I also checked the account_list.xml file it looks fine.
JAVA Memory arguments: -Xms2048m -Xmx2048m -XX:MaxPermSize=128m
WLS Start Mode=Production
CLASSPATH=:/opt/bea/bea91/patch_weblogic910/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/opt/bea/Java5/jdk1.5.0_17/lib/tools.jar:/opt/bea/bea91/weblogic91/server/lib/weblogic_sp.jar:/opt/bea/bea91/weblogic91/server/lib/weblogic.jar:/opt/bea/bea91/weblogic91/server/lib/webservices.jar::/opt/bea/bea91/weblogic91/common/eval/pointbase/lib/pbclient51.jar:/opt/bea/bea91/weblogic91/server/lib/xqrl.jar::/opt/bea/bea91/weblogic91/integration/lib/util.jar:
PATH=/opt/bea/bea91/weblogic91/server/bin:/opt/bea/Java5/jdk1.5.0_17/jre/bin:/opt/bea/Java5/jdk1.5.0_17/bin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/home/weblogic/bin
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://hostname:port/console *
starting weblogic with Java version:
java version "1.5.0_17"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_17-b04)
Java HotSpot(TM) Server VM (build 1.5.0_17-b04, mixed mode)
Starting WLS with line:
/opt/bea/Java5/jdk1.5.0_17/bin/java -server -Xms2048m -Xmx2048m -XX:MaxPermSize=128m -da -Dplatform.home=/opt/bea/bea91/weblogic91 -Dwls.home=/opt/bea/bea91/weblogic91/server -Dwli.home=/opt/bea/bea91/weblogic91/integration -Dweblogic.management.discover=true -Dweblogic.ProductionModeEnabled=true -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole= -Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0 -Djava.security.auth.login.config=/opt/bea/bea91/alsr21/conf/jaas.config -Dweblogic.ext.dirs=/opt/bea/bea91/patch_weblogic910/profiles/default/sysext_manifest_classpath -Dweblogic.Name=zsoaLAALSRAdminServer -Djava.security.policy=/opt/bea/bea91/weblogic91/server/lib/weblogic.policy weblogic.Server
<Dec 23, 2008 11:02:49 AM PST> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:
/opt/bea/bea91/user_projects/domains/zsoaLALASRDomain/lib/db2jcc2.jar:/opt/bea/bea91/user_projects/domains/zsoaLALASRDomain/lib/db2jcc_license_cu2.jar>
<Dec 23, 2008 11:02:49 AM PST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 1.5.0_17-b04 from Sun Microsystems Inc.>
<Dec 23, 2008 11:02:50 AM PST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 9.1 Mon Dec 12 19:26:33 EST 2005 689178 >
<Dec 23, 2008 11:02:53 AM PST> <Info> <WebLogicServer> <BEA-000215> <Loaded License : /opt/bea/bea91/license.bea>
<Dec 23, 2008 11:02:53 AM PST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Dec 23, 2008 11:02:53 AM PST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Dec 23, 2008 11:02:53 AM PST> <Notice> <Log Management> <BEA-170019> <The server log file /opt/bea/bea91/user_projects/domains/zsoaLALASRDomain/servers/zsoaLAALSRAdminServer/logs/zsoaLAALSRAdminServer.log is opened. All server side log events will be written to this file.>
<Dec 23, 2008 11:02:53 AM PST> <Error> <Socket> <BEA-000438> <Unable to load performance pack. Using Java I/O instead. Please ensure that libmuxer library is in :'/opt/bea/Java5/jdk1.5.0_17/jre/lib/i386/server:/opt/bea/Java5/jdk1.5.0_17/jre/lib/i386:/opt/bea/Java5/jdk1.5.0_17/jre/../lib/i386:/opt/bea/bea91/patch_weblogic910/profiles/default/native:/opt/bea/bea91/weblogic91/server/native/linux/x86_64:/opt/bea/bea91/weblogic91/server/native/linux/x86_64/oci920_8'
>
<Dec 23, 2008 11:02:54 AM PST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Dec 23, 2008 11:02:56 AM PST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Dec 23, 2008 11:02:56 AM PST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
INFO: com.systinet.wasp.WaspImpl - Starting Systinet Server for Java/6.0 (Java/1.5.0_17; Linux/2.6.9-78.0.1.ELsmp; build SSJ-6.0-20060622-1136)
INFO: com.systinet.wasp.monitoring.LogEventModule - Starting event management
INFO: log4j.Log4JAdapter - Events Log File: /opt/bea/bea91/user_projects/domains/zsoaLALASRDomain/servers/zsoaLAALSRAdminServer/tmp/_WL_user/registry/4rin9e/public/systinetRegistry_logEvents.log
INFO: log4j.Log4JAdapter - Error Events Log File: /opt/bea/bea91/user_projects/domains/zsoaLALASRDomain/servers/zsoaLAALSRAdminServer/tmp/_WL_user/registry/4rin9e/public/systinetRegistry_errorEvents.log
INFO: com.idoox.config.xml.ConfigStore - Starting configStore with savingPeriod 2000
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [system][http://systinet.com/wasp/app/core_services_client][core_services_client][6.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [system][http://systinet.com/wasp/app/builtin_serialization][builtin_serialization][6.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [system][http://systinet.com/wasp/app/security_providers][security_providers][1.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [system][http://systinet.com/wasp/app/uddi/redirect/5.0][uddi-redirect][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/wasp/app/uddi/6.0][UDDI-services][6.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/statistics/5.0][Statistics-client][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/xslt2uddi/v3/5.5][UDDIClient-xslt2uddi-v3][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/api/ext/5.0][UDDIClient-ext][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/approval_production/5.0][Approval-production-client][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/wsdl2uddi/v3/5.5][UDDIClient-wsdl2uddi-v3][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/approval_management/5.0][Approval-management-client][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/configuratorCluster/5.0][Configurator-cluster-client][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/replication/v3/5.0][Replication-client-v3][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/subscription/listener/v3/5.0][UDDIClient-subscription-listener-v3][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/approval/5.0][Approval-client-v3][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/taxonomy/v3/5.5][Taxonomy-client-v31][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/inquiryUI/6.0][UDDIClient-v3-ui][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/validate-values/v1/5.0][UDDIClient-validate-values-v1][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/custody/v3/5.0][UDDIClient-custody-v3][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/subscription/v3/ext/6.0][UDDIClient-subscription-v3-ext][6.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/administrationUtils/5.5][AdministrationUtils-client][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/wasp/app/bsc/web/6.0][bsc][6.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/transformer_kr/5.5][Transformer-kr-client][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/v3/5.0][UDDIClient-v3][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/wsdl2uddi/v2/5.0][UDDIClient-wsdl2uddi-v2][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/validate-values/v2/5.0][UDDIClient-validate-values-v2][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/v3_ext/5.0][UDDIClient-v3_ext][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/xml2uddi/v3/5.5][UDDIClient-xml2uddi-v3][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/value-set-caching/v3/5.0][UDDIClient-value-set-caching-v3][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/xsd2uddi/v3/5.5][UDDIClient-xsd2uddi-v3][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/wasp/app/uddi/web/6.0][UDDI-web][6.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/approval_checker/5.0][Approval-checker-client-v3][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/category/v3/5.5][Category-client-v3][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/group/5.5][Group-client][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/subscription/v3/5.0][UDDIClient-subscription-v3][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/v2/5.0][UDDIClient-v2][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/configurator/5.0][Configurator-client][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/permission/5.5][Permission-client][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/taxonomy/v3/5.0][Taxonomy-client-v3][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/v1/5.0][UDDIClient-v1][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/account/5.5][Account-client][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client/value-set-validation/v3/5.0][UDDIClient-value-set-validation-v3][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Registering package [uddi][http://systinet.com/uddi/client-core/5.0][Client-core][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [system][http://systinet.com/wasp/app/core_services_client][core_services_client][6.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [system][http://systinet.com/wasp/app/builtin_serialization][builtin_serialization][6.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [system][http://systinet.com/wasp/app/uddi/redirect/5.0][uddi-redirect][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [system][http://systinet.com/wasp/app/security_providers][security_providers][1.0]
INFO: com.idoox.wasp.security.server.SecurityModule - SecurityModule starts.
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client-core/5.0][Client-core][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/statistics/5.0][Statistics-client][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/approval_management/5.0][Approval-management-client][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/replication/v3/5.0][Replication-client-v3][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/transformer_kr/5.5][Transformer-kr-client][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/v3/5.0][UDDIClient-v3][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/v2/5.0][UDDIClient-v2][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/configurator/5.0][Configurator-client][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/v1/5.0][UDDIClient-v1][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/account/5.5][Account-client][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/xslt2uddi/v3/5.5][UDDIClient-xslt2uddi-v3][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/api/ext/5.0][UDDIClient-ext][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/wsdl2uddi/v3/5.5][UDDIClient-wsdl2uddi-v3][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/inquiryUI/6.0][UDDIClient-v3-ui][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/custody/v3/5.0][UDDIClient-custody-v3][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/administrationUtils/5.5][AdministrationUtils-client][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/v3_ext/5.0][UDDIClient-v3_ext][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/xml2uddi/v3/5.5][UDDIClient-xml2uddi-v3][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/value-set-caching/v3/5.0][UDDIClient-value-set-caching-v3][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/xsd2uddi/v3/5.5][UDDIClient-xsd2uddi-v3][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/category/v3/5.5][Category-client-v3][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/subscription/v3/5.0][UDDIClient-subscription-v3][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/taxonomy/v3/5.0][Taxonomy-client-v3][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/value-set-validation/v3/5.0][UDDIClient-value-set-validation-v3][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/approval/5.0][Approval-client-v3][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/wsdl2uddi/v2/5.0][UDDIClient-wsdl2uddi-v2][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/validate-values/v2/5.0][UDDIClient-validate-values-v2][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/configuratorCluster/5.0][Configurator-cluster-client][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/validate-values/v1/5.0][UDDIClient-validate-values-v1][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/group/5.5][Group-client][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/permission/5.5][Permission-client][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/subscription/listener/v3/5.0][UDDIClient-subscription-listener-v3][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/subscription/v3/ext/6.0][UDDIClient-subscription-v3-ext][6.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/taxonomy/v3/5.5][Taxonomy-client-v31][5.5]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/approval_checker/5.0][Approval-checker-client-v3][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/uddi/client/approval_production/5.0][Approval-production-client][5.0]
INFO: com.systinet.wasp.admin.PackageRepositoryImpl - Loading package [uddi][http://systinet.com/wasp/app/uddi/6.0][UDDI-services][6.0]
[Fatal Error] account_list.xml:1:1: Premature end of file.
<Dec 23, 2008 11:03:04 AM PST> <Error> <HTTP> <BEA-101216> <Servlet: "Registry Servlet" failed to preload on startup in Web application: "registry.war".
java.lang.ExceptionInInitializerError
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:242)
at com.systinet.uddi.security.destination.DestinationSecurityModule.load(DestinationSecurityModule.java:25)
at com.idoox.wasp.ModuleRepository.loadModule(ModuleRepository.java:120)
org.xml.sax.SAXParseException: Premature end of file.
at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at com.idoox.config.xml.XMLConfigurator.prepareConfigFile(XMLConfigurator.java:575)
at com.idoox.config.xml.XMLConfigurator.init(XMLConfigurator.java:420)
at com.idoox.config.xml.XMLConfigurator.init(XMLConfigurator.java:333)
Truncated. see log file for complete stacktrace
>
<Dec 23, 2008 11:03:04 AM PST> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'registry'.
weblogic.application.ModuleException: [HTTP:101216]Servlet: "Registry Servlet" failed to preload on startup in Web application: "registry.war".
<Dec 23, 2008 11:03:04 AM PST> <Notice> <WebLogicServer> <BEA-000329> <Started WebLogic Admin Server "zsoaLAALSRAdminServer" for domain "zsoaLALASRDomain" running in Production Mode>
<Dec 23, 2008 11:03:04 AM PST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<Dec 23, 2008 11:03:04 AM PST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
Exception in thread "Timer-3" java.lang.NoClassDefFoundError: com/systinet/wasp/webservice/FinalizationSupport
at com.systinet.wasp.ServiceManagerImpl$ReferenceQueueCleaner.run(ServiceManagerImpl.java:2617)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)I discovered, that the problem is probably caused by a collection, which is returned by a findBy method.
see detail of exception:
Caused by: javax.xml.bind.JAXBException: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 1 counts of IllegalAnnotationExceptions
java.util.Collection is an interface, and JAXB can't handle interfaces.
this problem is related to the following location:
at java.util.Collection
When I deploy an simple WS (summerizing 2 numbers) it is deployed fine and the WS is up and running.
Does anyone has experienced a similar problem? I want to expose the functionality of my BO methods in order to set up a small POC.
Can anyone please help?
Thanks & Regards,
Michael
null -
DB2 zOS database export tips & tricks
Does anyone have compiled or know of the existence of a list of tips, pointers, tricks, etc. for the process of exporting a DB2 zOS database (for use in a later import into a DB2 LUW system)?
Most appreciated any help you may provide.
Regards,
Julio Porras.I just uploaded a document with the steps that I followed for the DB2 z/OS database export.
Mind I did this back in October, 2008 (see my original post date).
You can find the document here:
http://scn.sap.com/docs/DOC-45835
I hope you find it helpful.
Regards,
JP. -
Exporting data clusters with type version
Hi all,
let's assume we are saving some ABAP data as a cluster to database using the IMPORT TO ... functionality, e.g.
EXPORT VBAK FROM LS_VBAK VBAP FROM LT_VBAP TO DATABASE INDX(QT) ID 'TEST'
Some days later, the data can be imported
IMPORT VBAK TO LS_VBAK VBAP TO LT_VBAP FROM DATABASE INDX(QT) ID 'TEST'.
Some months or years later, however, the IMPORT may crash: Since it is the most normal thing in the world that ABAP types are extended, some new fields may have been added to the structures VBAP or VBAK in the meantime.
The data are not lost, however: Using method CL_ABAP_EXPIMP_UTILITIES=>DBUF_IMPORT_CREATE_DATA, they can be recovered from an XSTRING. This will create data objects apt to the content of the buffer. But the component names are lost - they get auto-generated names like COMP00001, COMP00002 etc., replacing the original names MANDT, VBELN, etc.
So a natural question is how to save the type info ( = metadata) for the extracted data together with the data themselves:
EXPORT TYPES FROM LT_TYPES VBAK FROM LS_VBAK VBAP FROM LT_VBAP TO DATABASE INDX(QT) ID 'TEST'.
The table LT_TYPES should contain the meta type info for all exported data. For structures, this could be a DDFIELDS-like table containing the component information. For tables, additionally the table kind, key uniqueness and key components should be saved.
Actually, LT_TYPES should contain persistent versions of CL_ABAP_STRUCTDESCR, CL_ABAP_TABLEDESCR, etc. But it seems there is no serialization provided for the RTTI type info classes.
(In an optimized version, the type info could be stored in a separate cluster, and being referenced by a version number only in the data cluster, for efficiency).
In the import step, the LT_TYPES could be imported first, and then instances for these historical data types could be created as containers for the real data import (here, I am inventing a class zcl_abap_expimp_utilities):
IMPORT TYPES TO LT_TYPES FROM DATABASE INDX(QT) ID 'TEST'.
DATA(LO_TYPES) = ZCL_ABAP_EXPIMP_UITLITIES=>CREATE_TYPE_INFOS ( LT_TYPES ).
assign lo_types->data_object('VBAK')->* to <LS_VBAK>.
assign lo_types->data_object('VBAP')->* to <LT_VBAP>.
IMPORT VBAK TO <LS_VBAK> VBAP TO <LT_VBAP> FROM DATABASE INDX(QT) ID 'TEST'.
Now the data can be recovered with their historical types (i.e. the types they had when the export statement was performed) and processed further.
For example, structures and table-lines could be mixed into the current versions using MOVE-CORRESPONDING, and so on.
My question: Is there any support from the standard for this functionality: Exporting data clusters with type version?
Regards,
RüdigerThe IMPORT statement works fine if target internal table has all fields of source internal table, plus some additional fields at the end, something like append structure of vbak.
Here is the snippet used.
TYPES:
BEGIN OF ty,
a TYPE i,
END OF ty,
BEGIN OF ty2.
INCLUDE TYPE ty.
TYPES:
b TYPE i,
END OF ty2.
DATA: lt1 TYPE TABLE OF ty,
ls TYPE ty,
lt2 TYPE TABLE OF ty2.
ls-a = 2. APPEND ls TO lt1.
ls-a = 4. APPEND ls TO lt1.
EXPORT table = lt1 TO MEMORY ID 'ZTEST'.
IMPORT table = lt2 FROM MEMORY ID 'ZTEST'.
I guess IMPORT statement would behave fine if current VBAK has more fields than older VBAK. -
EXP utillity has higher version than database - export failed !
Hi,
I have a Oracle8 Enterprise Edition Release 8.0.5.0.0 database on our server and I have installed a 9i client on my PC. Now I have to use the export utility to export a specific table from our DB, but as I read from 'Oracle9i Database Utilities' book:
"The version of the Export utility must be equal to the lowest version of the source or target database".
So, I guess I need to install a 8.0.5 client on my PC (I have W2K) but nobody can give me the install CD in the company:(
I've looked on the OTN page if I can find the needed version, but I found only the 8i (8.1.7) install kit. Do you think it shall work the EXP utility if I install that ? Or can I find somewhere else the 8.0.5 install kit ?
Thanks:
Szilard
PS: the error message what I got when I tried to export with 9i client from 8.0.5 DB:
C:\exp user/passw file=myexp.dmp tables=emp;
EXP-00056: ORACLE error 2248 encountered
ORA-02248: invalid option for ALTER SESSION
EXP-00000: Export terminated unsuccessfully
, but the same command line from a 9i DB worked...Since your target server is 8.0.5, you should have the EXP utility from a 8.0.x versions. Anything higher will not work.
HTH. -
RCVCAT database is not compatible with this version of RMAN
I am getting the below error while trying to configure rman catalog datababse.
rman target prod_dba/Pass1234@proddb catalog cat_dba/Pass1234@catdb
Recovery Manager: Release 9.2.0.1.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to target database: TESTDB (DBID=2409515669)
connected to recovery catalog database
recovery catalog is not installed
RMAN>
RMAN> register database;
recovery catalog is not installed
recovery catalog is not installed
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of register command at 07/20/2007 19:05:40
RMAN-06429: RCVCAT database is not compatible with this version of RMAN
RMAN>
And Oracle version is same in proddb and catdb
SQL> select * from v$version;
BANNER
Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
PL/SQL Release 9.2.0.1.0 - Production
CORE 9.2.0.1.0 Production
TNS for 32-bit Windows: Version 9.2.0.1.0 - Production
NLSRTL Version 9.2.0.1.0 - Production
any inputs...
Thanks.Hi,
when upgrading catalog am getting the error like,
error occurred in source file: krmk.pc, line: 6986
text of failing SQL statement: ╠≥`☺
ORACLE error from recovery catalog database: ORA-00942: table or view does not e
xist
error occurred in source file: krmk.pc, line: 6986
text of failing SQL statement: ╠≥`☺
ORACLE error from recovery catalog database: ORA-00942: table or view does not e
xist
error occurred in source file: krmk.pc, line: 6986
text of failing SQL statement:µ`☺
ORACLE error from recovery catalog database: ORA-00942: table or view does not e
xist
Whether i need to run catpath.sql etc on the db? -
TARGET database is not compatible with this version of RMAN
I am trying to register a database (version 8.0.4) on my catalog database which is version 8.1.7.
I get the following error:
RMAN-06185: Recovery Manager incompatible with TARGET database: RMAN 8.0.4 to 8.0.4 required
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-06429: TARGET database is not compatible with this version of RMAN
Does this mean that my RMAN database has to be 8.0.4 ?
What happens if my RMAN database is 8.0.4 and target is 8.1.7 ?
Thanks for any help,
Sameercheck RMAN compatibility matrix
Target/Auxiliary Database|| RMAN Executable|| Catalog Database ||Catalog Schema
8.0.3 8.0.3 >=8.x 8.0.3
8.0.4 8.0.4 >=8.x >= 8.0.4, see "Note 2: 8.1 or Later Catalog Schemas and 8.0 Target Databases"
8.0.5 8.0.5 >=8.x >= 8.0.5, see "Note 2: 8.1 or Later Catalog Schemas and 8.0 Target Databases"
8.0.6 8.0.6 >=8.x 8.0.6
8.0.6 8.0.6 >=8.1.x >=8.1.x
8.1.5 8.1.5 >=8.1.x >= 8.1.5
8.1.6 8.0.6.1 >=8.x 8.0.6
8.1.6 8.0.6.1 >=8.1.x >= 8.1.x
8.1.6 8.1.x >=8.1.x >= RMAN executable
8.1.7 8.0.6.1 >=8.x 8.0.6
8.1.7 8.0.6.1 >=8.1.x >=8.1.x
8.1.7 8.1.x >=8.1.x >= RMAN executable
9.0.1 >=9.0.1 >=8.1.x >= RMAN executable
In other words to backup 8.0.4 version u need a separate schema in catalog database and which will be only used for 8.0.4 -
TARGET database is not compatible with RMAN version
Hi all,
we have an issue related to RMAN version.
A few weeks ago we update our 10.2.0.1 Oracle Database to 10.2.0.4 using 6810189 pacth set.
Now when we try to execute RMAN this is the output:
Recovery Manager : Release 11.1.0.6.0 - Production on Jue Nov 20 12:20:57 2008
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Recovery Manager incompatible with TARGET database: RMAN 8.0.4.0 to 10.2.0.4 needed
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-06429: TARGET database is not compatible with this version of RMAN
(I translate the spanish message, maybe the words is not exactly the same in the english version)
As is shown in the output the RMAN version installed by the pacthset is higher than database version, is there a way to downgrade RMAN or to solve this issue?
Thanks in advance,
AlexI'm pretty sure patchset 6810189 does not install RMAN executable 11g. I did several patchings to 10.2.0.4 and that never happened. Patching may sometimes leave components at a lower level than the patchset,but never the opposite is true. That would be definitely a bug. So you (or someone else) installed 11g software.
Werner -
RMAN-06429: TARGET database is not compatible with this version of RMAN
he Hi,
how can i solve this issue . how i will upgrade the Rman. My production database details are below
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
PL/SQL Release 10.2.0.1.0 - Production
CORE 10.2.0.1.0 Production
TNS for 32-bit Windows: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production
while i'm configuring rman i'm getting below error . please help me.
C:\Documents and Settings\vj.dcruz>rman target / catalog rman01/rman01@upp
Recovery Manager: Release 11.2.0.1.0 - Production on Wed Sep 14 08:18:02 2011
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
Recovery Manager incompatible with TARGET database: RMAN 8.0.4.0 to 10.2.0.0 required
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-06429: TARGET database is not compatible with this version of RMAN
rgds,
johnJohnvd wrote:
Hi Hemant,
i'm doing same thing login 10.2.0.0 database and configure the rman but while connect target its saying that my Recovery Manager: Release 11.2.0.1.0 - Production on Wed Sep 14 09:04:59 2011
how its happening is there any where i have to change the path.
Regards,
johnJohn, you need to use the RMAN binary which is located in bin folder of Oracle Database (ie /u01/oracle/product/10.2/db1/bin). You shouldn't use "rman which comes with Oracle 11g client".
If you are using windows, run the following commands in command prompt and then copy/paste the output:
echo 5ORACLE_HOME%
echo %PATH%
If you are using unix, run the following commands in terminal and then copy/paste the output:
echo $ORACLE_HOME
echo $PATH
Regards
Gokhan -
RMAN-06429: RCVCAT database is not compatible with this version of RMAN
Hi There,
I just want to confirm there is no work around for the issue I am having. Here is my situation:
I have four Oracle 8i databases that can not be removed because of client requirements. These 8i databases have there own RMAN catalog which is 10G (Originally there were Oracle 8i, 9i and 10g databases using it but are now moved to 11g catalog). Databases are backing up fine. However, all the other databases are using the RMAN 11g Catalog. I want to point the Oracle 8i databases to point to the RMAN 11g recovery catalog. I created an 8i schema, however, i'm getting the following error message: RMAN-06429: RCVCAT database is not compatible with this version of RMAN. It's pretty straight forward, however, I wanted to put the question out there to see if there are any work arounds. I would prefer to have only one RMAN recovery catalog.
Thanks in advance.
JHello;
I know of no way around the RMAN Compatibility Matrix. I would keep a second catalog DB for these older databases. Or go NOCATALOG. I checked all my sources and if there's a better option I sure did not find it. What breaks if these go to Oracle 9?
http://arjudba.blogspot.com/2010/03/about-rman-compatibility-matrix.html
Ask Tom
http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:518622203320
Additional Information :
OERR: RMAN 6429 %s database is not compatible with this version of RMAN [ID 70776.1]
RMAN-06439: Compatibility Between 8.1.5 RMAN Executable and 8.1.6 Catalog [ID 104728.1]
Best Regards
mseberg
Edited by: mseberg on Sep 7, 2012 8:27 AM
Edited by: mseberg on Sep 7, 2012 10:53 AM -
Hello All,
I am getting this error while I am connecting my access database website for the change
"This database was connected to a Microsoft Access Services site that is not compatible with this version of Microsof Access. You cannot make design changes or modify data in database."
I am using SharePoint 2010 and Microsoft Office 2010.
I have created one Contact Database Site and now I am trying to modify the layout of the form in Access. and I am getting the error that I have mentioned.
Please provide help on it.
Thanks in Advance....Hello All,
I got the answer, we have to enable the port 80 or where the access service is deployed and we have to change Trust setting and also, enable the macro from Access.
Hope this will help to other.... -
Hi! Why is the version file smaller than the original file, although I didn't make changes in the file? And why is the keywords don't exporting with original files?
Wild guess: you're using the the wrong export settings. You'll need to tell us more before we can help you - like the export settings you're usng, the size and format of the originals etc.
Maybe you are looking for
-
Open and close posting periods for at ledger level
Hello, We are running on ECC6 with the new ledger. We have activated two ledgers (the leading ledger and a non-leading ledger for group reporting). Our client would like to manage the posting period at ledger level. Example: during the month closing,
-
Hi all, What is Infopackage Groups and what are the settings in side thanks in advance regards
-
I tried to delete a calendar while in the app, but now it says the action is not supported in the server? There is also a pop-up that appears every 30 seconds to tell me about the error.
-
Hi All, Can any body tell me, "How to enter data into Database table using the screen element table control" Reply me to [email protected] Regards, Kiran
-
Acrobat und Outlook: keine gültige Seriennummer für Acrobat gefunden
Hallo, Acrobat 8 Standard auf Windows 7 (64 Bit) ist lizensiert und aktiviert und funktioniert soweit problemlos und unauffällig. Die Add-ons unter Office 2010 machten Ärger und sind deaktiviert, werden aber auch nicht benötigt. Allerdings kommt im A