Database export
if i export the database for backup it saves the .dmp file on default location in "C:\Documents and Settings\user". if i want to change that location how to change that?
1) Although a dump file is a logical backup, I sincerely hope you are not using it as your primary method of backing up a database. You need physical backups (RMAN or user-managed). Logical backups can compliment but not replace physical backups.
2) You could certainly schedule the export utility to run regularly and to write files to whatever location you desire. It would be exceedingly unusual to want a full database export every hour however. That generally implies that you're doing something wrong.
3) This doesn't appear to relate to database security. It would probably be more appropriate in the Export/Import/SQL Loader and External Tables forum or even in the Database - General forum.
Justin
Edited by: Justin Cave on Jun 23, 2012 1:30 AM
Similar Messages
-
Unable to retrieve nametab info for logic table BSEG during Database Export
Hi,
Our aim is to Migrate to New hardware and do the Database Export of the existing System(Unicode) and Import the same in the new Hardware
I am doing Database Export on SAP 4.7 SR1,HP-UX ,Oracle 9i(Unicode System) and during Database Export "Post Load Processing phase" got the error as mentioned in SAPCLUST.log
more SAPCLUST.log
/sapmnt/BIA/exe/R3load: START OF LOG: 20090216174944
/sapmnt/BIA/exe/R3load: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#20
$ SAP
/sapmnt/BIA/exe/R3load: version R6.40/V1.4 [UNICODE]
Compiled Aug 13 2007 16:20:31
/sapmnt/BIA/exe/R3load -ctf E /nas/biaexp2/DATA/SAPCLUST.STR /nas/biaexp2/DB/DDLORA.T
PL /SAPinst_DIR/SAPCLUST.TSK ORA -l /SAPinst_DIR/SAPCLUST.log
/sapmnt/BIA/exe/R3load: job completed
/sapmnt/BIA/exe/R3load: END OF LOG: 20090216174944
/sapmnt/BIA/exe/R3load: START OF LOG: 20090216182102
/sapmnt/BIA/exe/R3load: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#20
$ SAP
/sapmnt/BIA/exe/R3load: version R6.40/V1.4 [UNICODE]
Compiled Aug 13 2007 16:20:31
/sapmnt/BIA/exe/R3load -datacodepage 1100 -e /SAPinst_DIR/SAPCLUST.cmd -l /SAPinst_DI
R/SAPCLUST.log -stop_on_error
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
(GSI) INFO: dbname = "BIA20071101021156
(GSI) INFO: vname = "ORACLE "
(GSI) INFO: hostname = "tinsp041
(GSI) INFO: sysname = "HP-UX"
(GSI) INFO: nodename = "tinsp041"
(GSI) INFO: release = "B.11.11"
(GSI) INFO: version = "U"
(GSI) INFO: machine = "9000/800"
(GSI) INFO: instno = "0020293063"
(EXP) TABLE: "AABLG"
(EXP) TABLE: "CDCLS"
(EXP) TABLE: "CLU4"
(EXP) TABLE: "CLUTAB"
(EXP) TABLE: "CVEP1"
(EXP) TABLE: "CVEP2"
(EXP) TABLE: "CVER1"
(EXP) TABLE: "CVER2"
(EXP) TABLE: "CVER3"
(EXP) TABLE: "CVER4"
(EXP) TABLE: "CVER5"
(EXP) TABLE: "DOKCL"
(EXP) TABLE: "DSYO1"
(EXP) TABLE: "DSYO2"
(EXP) TABLE: "DSYO3"
(EXP) TABLE: "EDI30C"
(EXP) TABLE: "EDI40"
(EXP) TABLE: "EDIDOC"
(EXP) TABLE: "EPIDXB"
(EXP) TABLE: "EPIDXC"
(EXP) TABLE: "GLS2CLUS"
(EXP) TABLE: "IMPREDOC"
(EXP) TABLE: "KOCLU"
(EXP) TABLE: "PCDCLS"
(EXP) TABLE: "REGUC"
myCluster (55.16.Exp): 1557: inconsistent field count detected.
myCluster (55.16.Exp): 1558: nametab says field count (TDESCR) is 305.
myCluster (55.16.Exp): 1561: alternate nametab says field count (TDESCR) is 304.
myCluster (55.16.Exp): 1250: unable to retrieve nametab info for logic table BSEG
myCluster (55.16.Exp): 8033: unable to retrieve nametab info for logic table BSEG
myCluster (55.16.Exp): 2624: failed to convert cluster data of cluster item.
myCluster: RFBLG *003**IN07**0001100000**2007*
myCluster (55.16.Exp): 318: error during conversion of cluster item.
myCluster (55.16.Exp): 319: affected physical table is RFBLG.
(CNV) ERROR: data conversion failed. rc = 2
(RSCP) WARN: env I18N_NAMETAB_TIMESTAMPS = IGNORE
(DB) INFO: disconnected from DB
/sapmnt/BIA/exe/R3load: job finished with 1 error(s)
/sapmnt/BIA/exe/R3load: END OF LOG: 20090216182145
/sapmnt/BIA/exe/R3load: START OF LOG: 20090217115935
/sapmnt/BIA/exe/R3load: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#20
$ SAP
/sapmnt/BIA/exe/R3load: version R6.40/V1.4 [UNICODE]
Compiled Aug 13 2007 16:20:31
/sapmnt/BIA/exe/R3load -datacodepage 1100 -e /SAPinst_DIR/SAPCLUST.cmd -l /SAPinst_DI
R/SAPCLUST.log -stop_on_error
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
(GSI) INFO: dbname = "BIA20071101021156
(GSI) INFO: vname = "ORACLE "
(GSI) INFO: hostname = "tinsp041
(GSI) INFO: sysname = "HP-UX"
(GSI) INFO: nodename = "tinsp041"
(GSI) INFO: release = "B.11.11"
(GSI) INFO: version = "U"
(GSI) INFO: machine = "9000/800"
(GSI) INFO: instno = "0020293063"
myCluster (55.16.Exp): 1557: inconsistent field count detected.
myCluster (55.16.Exp): 1558: nametab says field count (TDESCR) is 305.
myCluster (55.16.Exp): 1561: alternate nametab says field count (TDESCR) is 304.
myCluster (55.16.Exp): 1250: unable to retrieve nametab info for logic table BSEG
myCluster (55.16.Exp): 8033: unable to retrieve nametab info for logic table BSEG
myCluster (55.16.Exp): 2624: failed to convert cluster data of cluster item.
myCluster: RFBLG *003**IN07**0001100000**2007*
myCluster (55.16.Exp): 318: error during conversion of cluster item.
myCluster (55.16.Exp): 319: affected physical table is RFBLG.
(CNV) ERROR: data conversion failed. rc = 2
(RSCP) WARN: env I18N_NAMETAB_TIMESTAMPS = IGNORE
(DB) INFO: disconnected from DB
SAPCLUST.l/sapmnt/BIA/exe/R3load: job finished with 1 error(s)
/sapmnt/BIA/exe/R3load: END OF LOG: 20090217115937
og (97%)
The main eror is "unable to retrieve nametab info for logic table BSEG "
Your reply to this issue is highly appreciated
Thanks
SunilHello,
acording to this output:
/sapmnt/BIA/exe/R3load -datacodepage 1100 -e /SAPinst_DIR/SAPCLUST.cmd -l /SAPinst_DI
R/SAPCLUST.log -stop_on_error
you are doing the export with a non-unicode SAP codepage. The codepage has to be 4102/4103 (see note #552464 for details). There is a screen in the sapinst dialogues that allows the change of the codepage. 1100 is the default in some sapinst versions.
Best Regards,
Michael -
How can I include Java objects in a 'Database Export'?
I am running a 'Database Export' to produce a DDL script for all objects in the schema.
I have some objects of type JAVA SOURCE and JAVA CLASS in my schema, but they are not included in the DDL script. Is there a way to get them included?
Version is 3.0.04.
Thanks,
MikeAny suggestions on this?
Thanks,
Mike -
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!!!! -
Error while database export in package SAPDODS_33 (Unicode conversion)
Hello,
I am performing Unicode conversion on an upgraded BI 7.0 system. This is running on AIX/DB2.
When I take database export for conversion, one package fails (SAPDODS_33) with error "The file system is full". In fact, df -k doesn't show that any file system is full.
I am taking the export to the following location: /db2/BWS/sapdata/EXPORT_DIR
There are 3 system-managed temporary tablespaces: PSAPTEMP, PSATEMP16 & SYSTOOLSTMPSPACE which were residing in /db2/BWS/saptemp1/NODE0000. This was getting full during the export. Now these temp.tablespaces have been relocated to a new file system of size 15GB.
But still the package SAPDODS_33 doesn't get exported. Could you please let me know how to solve this issue?
Thanks a lot!
Sundar.
=====================================================================================
SAPDODS_33.log
(DB) INFO: connected to DB
(rscpsumg) Please look also into "SAPDODS_33012.xml".
(rscpMC) Warn: env I18N_NAMETAB_TIMESTAMPS = IGNORE
(rscpMC) Warn: UMGCONTAINER has 1 problems.
(rscpMC) Warn: Global fallback code page = 1160
(rscpMC) Warn: Common character set is not 7-bit-ASCII
(rscpMC) Warn: Collision resolution method is 'fine'
(rscpMC) Warn: R3trans code pages = Normal
(rscpMC) Warn: EXPORT TO ... code pages = Normal
(rscpMC) Warn: Source is 'MDMP'
(rscpMC) Warn: I18N_NAMETAB_NORM_ALLOW = 0
(rscpMC) Warn: I18N_NAMETAB_NORM_LOG = 0
(rscpMC) Warn: I18N_NAMETAB_ALT_ALLOW = 0
(rscpMC) Warn: I18N_NAMETAB_ALT_LOG = 0
(rscpMC) Warn: I18N_NAMETAB_OLD_ALLOW = 0
(rscpMC) Warn: I18N_NAMETAB_OLD_LOG = 0
(GSI) INFO: dbname = "BWS
(GSI) INFO: vname = "DB6 "
(GSI) INFO: hostname = "UNKNOWN
(GSI) INFO: sysname = "AIX"
(GSI) INFO: nodename = "itmlartdev01x"
(GSI) INFO: release = "3"
(GSI) INFO: version = "5"
(GSI) INFO: machine = "002417CA4C00"
(GSI) INFO: instno = "0020169337"
(EXP) ERROR: DbSlExeRead failed
rc = 99, table "/BIC/B0000786000"
(SQL error -968)
error message returned by DbSl:
SQL0968C The file system is full. SQLSTATE=57011
(DB) INFO: disconnected from DB
/usr/sap/BWS/SYS/exe/run/R3load: job finished with 1 error(s)
/usr/sap/BWS/SYS/exe/run/R3load: END OF LOG: 20071211053119
p/sapinst/sapinst_instdir/NW04S/LM/COPY/DB6/EXP/CENTRAL/AS-ABAP/EXP #Hi Sundar,
if the problem is due to a high temp space usage. The root cause is typically the
sort during export. If the table is large, the sort spills to temp.
You can avoid the sort by doing an unsorted export or tweak the DB2 optimizer to use the primary key to do the sort.
Before DB2 9, you can reduce the OVERHEAD tablespace parameter to zero. Return this value to its previous value after the successful export. This is a indirect hint to the optimizer that random IOs are cheap. This might not help.
With DB2 9, this should not happen, because the DB2_OPT_MAX_TEMP_SIZE=10240 registry variable is set under DB2_WORKLOAD=SAP which limits the temp space usage to 10GB if possible. You can reduce this parameter further if necessary. Another problem could be that the optimizer has chosen the wrong temp space. The optimizer choses the temp space with the largest amount of pages (not size).
Regards, Jens -
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. -
Is this a BUG??? Database Export not including Foreign Key Constraints
I'm using SQL Developer 1.5.4 with both the 59.47 and 59.59 patches installed. I want to do a database export from a 10g XE schema, and include all objects in the resulting DDL. So, I select ALL the checkboxes in the export wizard and when I get to Step 3 to specify objects, I don't see any of my constraints in the listbox... no foreign key constraints, no primary key constraints, no check constraints, nothing. Is this a bug, or is there a workaround, or what could I possibly be doing wrong? We want to be able to use the database export feature to easily transport and track modifications to our entire schema using source control compare.
Any help or alternate suggestions would be apprieciated.
Thanks,
MattThanks skutz, we just figured that out this morning. Also, it should be noted that you need to be logged in as the owner of the schema otherwise selecting nothing in the filter will give you nothing, but selecting items in the filter will give you those items even if you're not connected as the schema owner. I wonder if that is the detail of the Bug 8679318.
Edited by: mattsnyder on Jul 14, 2009 9:24 AM -
Database Export exporting data does not export time of date columns
Hi,
I'm trying to export some data using Database Export and for the date columns the resulting scripts truncates dates showing only the date part not the time one. If export from a query result the resulting script include all the information (date and time).
Does anyone has an idea on how to export all the date information using database export.
thanksYep, as Jim said, under Tools / Preferences / Database / NLS Parameters I changed Date Format to DD-MON-YYYY HH24:MI:SS
Seems to have done the trick. What's the significance of DD-MON-RR versus DD-MON-YY? -
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 -
Error on oracle database export ORA-04045 and ora-00600
Hi
I am getting following errors on database export
EXP-00008: ORACLE error 4045 encountered
ORA-04045: errors during recompilation/revalidation of CHEALTH1.oracle/gss/util/NLSLocale005
ORA-00600: internal error code, arguments: [26599], [1], [225], [], [], [], [], []
EXP-00000: Export terminated unsuccessfully
we have recently run initxml.sql for XML after upgrading from 9.2.0.1.0 to 9.2.0.4.0
any suggestions
kedarYes, you are in the wrong forum, but it sounds like you have your environment variable (or registry entry) for ORA_NLS33 pointing at the wrong directory.
Steve -
SQL Developer 1.5.1 - Database Export - Exporting Column Comments
I have tried using the Database Export tool in SQL Developer 1.5.1 to export statements for "comment on column" but with no success. Is there a way to get these statements included in the DDL?
rasberryWhen you select 'table' the comments are generated 'automatically'.
This is what you want? -
SQL Developer 3.2.20.09 - Database Export generating an unusable file
I am using the Database Export option in the tools menu to create a script to create schema objects. Unfortunately, the output of the script is not very usable. There seem to be extra '/' throughout the script. Here is a sample:
-- DDL for Sequence ADDL_INFO_GROUP_SEQ
CREATE SEQUENCE "ADDL_INFO_GROUP_SEQ" MINVALUE 1 MAXVALUE 2147483647 INCREMENT BY 1 START WITH 1 CACHE 1000 NOORDER CYCLE ;
-- DDL for Sequence ADDL_INFO_NAME_LANG_SEQ
CREATE SEQUENCE "ADDL_INFO_NAME_LANG_SEQ" MINVALUE 1 MAXVALUE 2147483647 INCREMENT BY 1 START WITH 1 CACHE 1000 NOORDER CYCLE ;
-- DDL for Sequence ADDL_INFO_VALUE_SEQ
CREATE SEQUENCE "ADDL_INFO_VALUE_SEQ" MINVALUE 1 MAXVALUE 2147483647 INCREMENT BY 1 START WITH 1 CACHE 1000 NOORDER CYCLE ;
-- DDL for Sequence ATTACHMENT_GROUP_SEQ
CREATE SEQUENCE "ATTACHMENT_GROUP_SEQ" MINVALUE 1 MAXVALUE 2147483647 INCREMENT BY 1 START WITH 1 CACHE 1000 NOORDER CYCLE ;
Obviously, having both the ';' at the end of the statement and the '/' on the following line will cause an error when the script is executed.
Has anyone else seen this kind of behavior?In SQLPlus, this script will attempt to create everything twice, resulting in
ORA-00955: name is already used by an existing objectfor each line.
If SQL Developer doesn't do this then its SQLPlus compatability is broken.
This is messy and undesirable for DDL statements, but will definitely result in the wrong behaviour if there are insert statements. -
SQL Developer - Database Export - Constraints not included in DDL
I have used the Database Export function available in the Tools menu but have been unsuccessful in getting the referential integrety and check contraints to export. These are the steps I take:
Environment: Windows XP Professional.
SQL Developer 1.5.1
Tools>Database Export
In Source/Destination I select the filename and the database source and check:
Show Schema
Terminator
Pretty Print
Add Force to Views
Include Grants
In Types to Export I check all except Data.
In Specify Objects I select the Schema I want to export.
None of the foreign_key or check constraints are shown but I select all of the objects.
Export Summary
File:C:\Documents and Settings\richardk.asbury\My Documents\EER\eer3.sql
Connection:ENVD
DDL Options
Show Schema
Terminator
Pretty Print
Add Force to Views
Necessary object dependencies will be included in export.
Tables
A_EMIS_TOXIC_DTL
A_EMIS_TOXIC_HDR
DSK_BLOB
PORTAL_AI_PROFILE
PORTAL_AI_XREF
PORTAL_USER
SUBJECT_ITEM_PARENT
SUBJ_ITEM_ATTRIBUTE
SUBJ_ITEM_COMMENTS
SUBJ_ITEM_QUANTITIES
SUBJ_ITEM_RELATED
Views
ACTIVITY_TASK_LIST_VW
AGENCY_INTEREST_ORG_XREF_VW
AGENCY_INTEREST_VW
A_EMIS_TOXIC_DTL_VW
A_EMIS_TOXIC_HDR_VW
DSK_CENTRAL_VW
MTB_ATTRIBUTE_DESC_VW
MTB_ATTRIB_ATTR_DESC_XREF_VW
MTB_MUNICIPALITY_VW
MTB_PARAMETER_VW
MTB_PERSON_TITLE_VW
MTB_PORTAL_SUBMITTAL_STATUS_VW
MTB_QUANTITY_TYPE_VW
MTB_QUANT_METHOD_VW
MTB_STATE_VW
MTB_SUBJECT_ITEM_ATTRIBUTE_VW
MTB_SUBJECT_ITEM_TYPE_VW
MTB_UNITS_VW
ORGANIZATION_VW
PERSON_VW
PORTAL_AI_PROFILE_VW
PORTAL_AI_XREF_VW
PORTAL_EMAIL_QUEUE_VW
PORTAL_USER_VW
SUBJECT_ITEM_VW
SUBJ_ITEM_COMMENTS_VW
SUBJ_ITEM_GENERAL_VW
SUBJ_ITEM_LOC_LAT_LONG_VW
Indexes
INDX_DSK_BLOB_BLOB_TITLE
PK_A_EMIS_TOXIC_DTL_ID
PK_A_EMIS_TOXIC_HDR_ID
PK_DSK_BLOB
PK_PORTAL_USER_ID
PK_SUBJECT_ITEM_PARENT
PK_SUBJECT_ITEM_RELATED
PK_SUBJ_ITEM_ATTRIB_ID
PK_SUBJ_ITEM_COMMENTS_ID
PK_SUBJ_ITEM_QUANT_ID
SYS_C0017821
Package Spec
MNG_DATA
MNG_USER
Package Body
MNG_DATA
MNG_USER
Procedures
All procedures will be exported.
Functions
All functions will be exported.
Triggers
A_EMIS_TOXIC_DTL_BEFINSUPD
A_EMIS_TOXIC_HDR_BEFINSUPD
PORTAL_AI_PROFILE_BEFINS
PORTAL_AI_XREF_BEFINS
PORTAL_USER_BEFINS
SUBJECT_ITEM_PARENT_BEFINSUPD
SUBJ_ITEM_ATTRIBUTE_BEFINSUPD
SUBJ_ITEM_COMMENTS_BEFINSUPD
SUBJ_ITEM_QUANTITIES_BEFINSUPD
SUBJ_ITEM_RELATED_BEFINSUPD
Types
All types will be exported.
Sequences
A_EMIS_TOXIC_DTL_SEQ
A_EMIS_TOXIC_HDR_SEQ
DSK_BLOB_SEQ
PORTAL_AI_PROFILE_SEQ
PORTAL_AI_XREF_SEQ
PORTAL_USER_SEQ
SUBJECT_ITEM_PARENT_SEQ
SUBJ_ITEM_ATTRIBUTE_SEQ
SUBJ_ITEM_COMMENTS_SEQ
SUBJ_ITEM_QUANTITIES_SEQ
SUBJ_ITEM_RELATED_SEQ
Materialized Views
All materialized views will be exported.
Materialized View Logs
All materialized view logs will be exported.
Synonymns
All synonyms will be exported.
Queues
All queues will be exported.
Queue Tables
All queue tables will be exported.
Database Links
All data base links will be exported.
There are numerous Check and Foreign_key constraints missing in created DDL.
Im I missing a step?
rasberryActually all tables were included and the Automatically Include Dependent Objects option was checked.
For an example, the first table exported A_EMIS_TOXIC_DTL had the following constraints:
FK_A_EMIS_TOXIC_DTL2HDR Foreign_Key
NN_A_EMIS_TOXIC_DTL_ID Check
PK_A_EMIS_TOXIC_DTL_ID Primary_Key
The primary key constraint was included in the DDL but none of the others. -
Problem with running database export
i try to run my database export which i normally do everyday and it works fine but of recent i started receiving this error
Exp00008:Oracle error 4063 encountered
Ora04063:package body dmsys.dbms_om_util has errors.
Ora 06508 :pl/sql could not find program unit being called.
Ora 06512: at "DMSYS.DBMS_DM_MODEL_EXP"line 89
"DMSYS.DBMS_DM_MODEL_EXP"line 763
Ora06512 : at line 1
Exp00083:The previous problem occured when calling DMSYS.DBMS_DM_MODEL_EXP.schema_info.exp.
export was terminated successfully with errors.
pls i need solutions immediatelyHello Ajani Abd-Rahman,
Maybe you should try to re-install the export catalog and then recompile all procs?
@?/rdbms/admin/catexp7.sql
@?/rdbms/admin/utlrp.sqlOr check on Metalink for a bug.
HTH,
Yoann. -
Hi
We are having a database 10g running on solaris OS. We are getting a new server and I need to move the data. This is what I am planning to do.
Take full database export from original server. (This includes tablespaces, all schemas and data)
Import in new server, from SYS schema once Oracle is installed. so all the schemas and objects are imported.
Can you let me know this approach is right any precautions to be taken?
Thanksuser625850 wrote:
Hi
We are having a database 10g running on solaris OS. We are getting a new server and I need to move the data. This is what I am planning to do.
Take full database export from original server. (This includes tablespaces, all schemas and data)
Import in new server, from SYS schema once Oracle is installed. so all the schemas and objects are imported.
Can you let me know this approach is right any precautions to be taken?
ThanksRMAN DUPLICATE -
Full database export hangs (Oracle9i rel2)
I recently migrated successfully from oracle8i rel 8.0. to oracle9i release 2,But now am not able to do a full database export.has anyone experienced this and whats the remedy?.
the text i get is listed below.
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.
C:\Documents and Settings\Administrator>exp system/manager@ORCL file=C:\orclbk\p
oll.dmp full=y
Export: Release 9.2.0.1.0 - Production on Tue Aug 9 18:36:13 2005
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to: Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production
Export done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
About to export the entire database ...
. exporting tablespace definitions
. exporting profiles
. exporting user definitions
. exporting roles
. exporting resource costs
. exporting rollback segment definitions
. exporting database links
. exporting sequence numbers
. exporting directory aliases
. exporting context namespaces
. exporting foreign function library names
. exporting PUBLIC type synonyms
. exporting private type synonyms
. exporting object type definitions
EXP-00090: cannot pin type "OE"."CUSTOMER_TYP"
EXP-00056: ORACLE error 22303 encountered
OCI-22303: type "OE"."CUSTOMER_TYP" not found
EXP-00056: ORACLE error 24323 encountered
ORA-24323: value not allowed
EXP-00000: Export terminated unsuccessfully
C:\Documents and Settings\Administrator>You have to run the export with the SYS user. This error may arise on any plattform ranging form 9.0.1 to 10.2.0.
C:\>exp "'sys/oracle as sysdba'" full=y
Maybe you are looking for
-
I have tried to dowload and update itunes on my PC. I have had an error message error 7 (windows error 126) several times. I have deleted the previous version of itunes and tried a clean install, with the same result. What am i doing wrong????
-
Hi everyone! I cannot hear the callar in my Iphone 3G 8GB ... I put it to the mobile phone shop to repair... but even they installed the new little voice speaker (in the top of the iphone)... the iphone still does not have any voice from the caller..
-
HR-stopping Get Pernr from triggering
hi, My selection-screen is combination of PNP + other Fields i am using GET PERNR to retrive values.. my Problem is that When no values is given in PNP fields , i want to Skip GET PERNR statement.but i am unable to do it.. Kindly give some solution.
-
Daylight Saving Time Changes for 2007
Hello Friends Sun's J2SE 1.4.2_11 has taekn care of the new Daylight Saving Time changes in accordance with The Energy Policy Act of 2005. Does anyone know if bea has incorporated same changes to their Jrockit, if so then starting which version. http
-
Music plays, playlists are there but the song list is empty!?
The strangest things has happened with iTunes 7.3.2 today: all the playlists are there, I can even play the music, but the song list window is totaly empty! How has this happened and what can I do to restore the list? I've checked the .xml library fi