Database Export problem (11.2.0.1)
hi all,
I am trying to export the database with the following command:
exp username/password@DEV FULL=Y File=C:\Export\dev.dmp log=C:\Export\dev.log
the user i am exporting have all the rights, all the objects are valid and still it is hanging on the system procedural and objects.
However other user can do export with same command and in the same database?
Please guide..
thanks
can you post the screen you are seeing after you issue the command?
Is there any error message in alert file saying any has trace generated??
check the status of the job running...
select owner_name,attached_sessions,job_name,state from dba_datapump_jobs;
here check you jobs details..
-Regards,
Saha
Similar Messages
-
Hello DB2 guru's,
we are performing a AIX 4.3 DB2 V7 database extract using R3LOAD. (DBEXPORT.R3S)
The database size is 350GB. (with a table of 50GB, and 8x 20GB)
The challange is that we only have 3 days to perform the export.
This is already the 3th try and still nog luck.
13 of 15 processes finish succesfully but he 2 left keep on running it seems.
Allthough the TEMPSPACE tablespaces keep growing, so I can imagine it is exporting the 50GB table.
Is there a way to determine which table it is processing, and maybe to have an indication of completion time ?
If found a java tool : MIGMON but have no experience in that.
All help or comments are welcome...
Thank you for your time
HansHi guys,
thank you for your feedback.
We get to 83% in the export process. 13 of the 15 processes completed.
If I then check the TEMP tablespaces I see them growing to 50 a 60GB.
And then they are emptied and I loose connection and can start over again.
My assumption is that the (1X50GB, 10X20GB tables are the cause)
What can you advice specifically to solve the problem with those big tables.
Can anyone give an example of the MIGMON / SPLIT tool ? Or another advice ?
very much appreciated !!!
thanks
Hans -
Keywords in Master file and AP database-- Export Problem.
I believe that I have a conflict with keywords. I believe that I have "baked in" keywords by writing IPTC to the Master files and then added more keywords which I am guessing are in the Aperture database and not "baked in". When I then look at exported images using the XMP sidecar file with Adobe Bridge all of the keywords do not show up. I want to experiment with Lightroom and I want all of the keywords.
My process has been:
1. Add keywords to images from the keywords panel.
2. Write the IPTC metadata to the master files.
3. Add more keywords to the images from the keywords panel.
4. Export the images using the File/Export Masters/Create IPTC4XMP sidecare file.
5. Look at the exported images in other applications (Bridge and PhotoMechanic).
How can I export using XMP sidecar files and have ALL the keywords be exported???
DickBYes, this is a known problem; sqldev distinguishes between the Constraint and the Index although the former implies the latter...
Regards,
K. -
while iam exporting essbase database user wants to retruive data urgently,but database mode is read only.is there any way for user to access tha data.could you please tell me if any
user10821118 wrote:
while iam exporting essbase database user wants to retruive data urgently,but database mode is read only.is there any way for user to access tha data.could you please tell me if anyread only, so if you want to retrieve, you can do that . What issue/problem are you facing .
Else, to retrieve to view should not be an issue
Sandeep Reddy Enti
HCC
http://hyperionconsultancy.com/ -
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. -
EXPORT Problem. when i choose USER mode, it is exporting full database
Dear OTN Members,
we have a system ORacle 8i, 8.1.3 database, we created a user with DBA role, when we want to export data for a perticular user, after giving USER MODE Option, it is doing full database export including sys, system etc.
what is the reason?
Thanks in advanceAny ideas please,
Still im looking for this solution. I have a " user" with DBS role, we are trying to export only this user, it is coming up to type of mode like
1)E ntire database 2)U 3) T ables >
we are choosing user mode, but all the time it si taking Entire databse, including, Systtem and other users eetc.
im struggling since 20 days. no success. Please -
Hi Expert , crystal report export problem. system not responding
Hi,
crystal report export problem. system not responding.
Thanks
Rajkumar GuptaDear Raj,
Please try this
Try
Dim oSubReport As CrystalDecisions.CrystalReports.Engine.SubreportObject
Dim rptSubReportDoc As CrystalDecisions.CrystalReports.Engine.ReportDocument
Dim rptView As New CrystalDecisions.Windows.Forms.CrystalReportViewer
Dim rptPath As String = System.Windows.Forms.Application.StartupPath & "\" & rptName
Dim rptDoc As New CrystalDecisions.CrystalReports.Engine.ReportDocument
rptDoc.Load(rptPath)
rptView.ShowExportButton = True
rptView.ReportSource = rptDoc
For Each oMainReportTable As CrystalDecisions.CrystalReports.Engine.Table In rptDoc.Database.Tables
oMainReportTable.Location = System.Windows.Forms.Application.StartupPath & "\" & SourceXML
Next
For Each rptSection As CrystalDecisions.CrystalReports.Engine.Section In rptDoc.ReportDefinition.Sections
For Each rptObject As CrystalDecisions.CrystalReports.Engine.ReportObject In rptSection.ReportObjects
If rptObject.Kind = CrystalDecisions.Shared.ReportObjectKind.SubreportObject Then
oSubReport = rptObject
rptSubReportDoc = oSubReport.OpenSubreport(oSubReport.SubreportName)
For Each oSubTable As CrystalDecisions.CrystalReports.Engine.Table In rptSubReportDoc.Database.Tables
oSubTable.Location = System.Windows.Forms.Application.StartupPath & "\" & SourceXML
Next
End If
Next
Next
'Setting Paper
Dim rawKind As Integer = 0
Dim printSet As New System.Drawing.Printing.PrinterSettings
For i As Integer = 0 To printSet.PaperSizes.Count - 1
If printSet.PaperSizes.Item(i).PaperName.ToUpper = PaperName.ToUpper Then
rawKind = CInt(printSet.PaperSizes.Item(i).RawKind)
Exit For
End If
Next
Dim MyTest As New SaveFileDialog
rptDoc.PrintOptions.PaperSize = CType(rawKind, CrystalDecisions.Shared.PaperSize)
rptDoc.ExportToStream(ExportFormatType.Excel)
'rptDoc.SaveAs("C:\TBKING.xls", True)
'''How to export the report
Try
Dim CrExportOptions As ExportOptions
Dim CrDiskFileDestinationOptions As New _
DiskFileDestinationOptions()
Dim rename As String
rename = rptName.Replace(".rpt", "")
Dim CrFormatTypeOptions As New ExcelFormatOptions
CrDiskFileDestinationOptions.DiskFileName = _
"c:\Report\" & rename & "_Export_File.xls"
CrExportOptions = rptDoc.ExportOptions
With CrExportOptions
.ExportDestinationType = ExportDestinationType.DiskFile
.ExportFormatType = ExportFormatType.Excel
.DestinationOptions = CrDiskFileDestinationOptions
.FormatOptions = CrFormatTypeOptions
End With
rptDoc.Export()
Catch ex As Exception
MsgBox(ex.ToString)
End Try
'' end by kevin shah
rptView.Show()
rptView.ShowExportButton = True
Dim oFrm As New System.Windows.Forms.Form
rptView.DisplayGroupTree = True
rptView.Dock = System.Windows.Forms.DockStyle.Fill
rptView.Location = New System.Drawing.Point(0, 0)
oFrm.AutoScaleBaseSize = New System.Drawing.Size(5, 13)
oFrm.Controls.Add(rptView)
oFrm.Name = "Report Viewer"
oFrm.Text = "Report Viewer11"
oFrm.ResumeLayout(True)
oFrm.WindowState = System.Windows.Forms.FormWindowState.Maximized
oFrm.TopMost = True
oFrm.ShowDialog()
Catch ex As Exception
objMain.objApplication.MessageBox(ex.Message)
End Try
By pressing this button XLS file be generated on C:\report\
Hope this will resolved the issue
Thanks
Kevin -
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 -
As far as I could see, a similar problem has been reported for earlier versions of SQL Developer, but still seems to apply for some parts in 4.0.0.13.80 under Windows7 64bit with JDK 1.7.0_45 64bit ...
Currently not all objects in a generated DDL using "Quick DDL" or "Tools - Database Export" are sorted evenly ... tables and foreign key constraints seem to be sorted, but common constraints are not.
This is rather annoying when trying to compare the generated scripts of two databases. Or trying to detect changes over lifetime (SVN etc.).
Or is there an option for this I could not find/see so far?
example output from database export of SQLDev 4.0.0.13.80 on the same machine, within some minutes, no configuration change, for a local and a remote database ...
from local:
Questions:
why are there blank lines added for the local database
why aren't the grants in the same order
local database
remote database
GRANT DELETE, INSERT, SELECT, UPDATE ON "FOREIGNSCHEMA"."TABLE_FOR_GRANT" TO "ACCESS_ROLE_FOR_SCHEMA_3";
GRANT REFERENCES ON "FOREIGNSCHEMA"."TABLE_FOR_GRANT" TO "SCHEMA_3";
GRANT REFERENCES ON "FOREIGNSCHEMA"."TABLE_FOR_GRANT" TO "SCHEMA_4";
GRANT SELECT, REFERENCES ON "FOREIGNSCHEMA"."TABLE_FOR_GRANT" TO "SCHEMA_5";
GRANT SELECT, REFERENCES ON "FOREIGNSCHEMA"."TABLE_FOR_GRANT" TO "SCHEMA_6";
GRANT SELECT ON "FOREIGNSCHEMA"."TABLE_FOR_GRANT" TO "SCHEMA_7";
GRANT REFERENCES ON "FOREIGNSCHEMA"."TABLE_FOR_GRANT" TO "SCHEMA_3";
GRANT REFERENCES ON "FOREIGNSCHEMA"."TABLE_FOR_GRANT" TO "SCHEMA_4";
GRANT SELECT, REFERENCES ON "FOREIGNSCHEMA"."TABLE_FOR_GRANT" TO "SCHEMA_5";
GRANT DELETE, INSERT, SELECT, UPDATE ON "FOREIGNSCHEMA"."TABLE_FOR_GRANT" TO "ACCESS_ROLE_FOR_SCHEMA_3";
GRANT SELECT, REFERENCES ON "FOREIGNSCHEMA"."TABLE_FOR_GRANT" TO "SCHEMA_6";
remark: missing SCHEMA_7 is okay, because it is not yet on the remote database
Similar applies to non foreign key constraints, where the unsorted output is even worse ...
Message was edited by: stuecklDid you ever figure out why SQL Developer isn't exporting the NOT NULL attribute of columns?
I'm running into that on a 9i database, but not on 11g.
Skip -
Could u help with oracle 8i export problem
hi
i'm facing a problem in
oracle engine which preventing them from execute the export command (full database export ) since it
always terminated abnormally and returns the following error:
EXP-0008 : Oracle error 6553
ORA-06553 PLS-561
the export terminated when it's start exporting synonyms
what can i do
thanksReally the errors does not point to any solution but It seems you have problems with the views in the data dictionary that works to export the synonyms.
I recommend you to get connection as sys and run this:
<ORACLE_HOME>/rdbms/admin/catexp.sql
try and replay
Joel Pérez -
ORA-29540 during full database export
Hi,
Anyone encounter this error ORA-29540 during full database export. Have check out the web site for solution. Have check that the init file compatible is set to 8.1.0, the public synonym dba_java is been removed. However after the above remedies, the problem still occured. My database version is 8.1.5. Please let me know if there is other solution to this problem.
Thank You ...
regards,
lbsHi,
Thanks...Any idea how to check whether the installation for the initjvm.sql is successful. cos I just took over from the previous DBA and he too have no idea...
Thank You.. -
while taking database export in ORACL8i it is terminating with errror. Please suggest remedial action. The messages given by system are appended below
Connected to: Oracle8i Enterprise Edition Release 8.1.5.0.0 - Production
With the Partitioning and Java options
PL/SQL Release 8.1.5.0.0 - Production
Export done in US7ASCII character set and US7ASCII NCHAR character set
About to export specified users ...
. exporting pre-schema procedural objects and actions
. exporting foreign function library names for user DEEPAK
. exporting object type definitions for user DEEPAK
About to export DEEPAK's objects ...
. exporting database links
. exporting sequence numbers
. exporting cluster definitions
. about to export DEEPAK's tables via Conventional Path ...
. . exporting table XX 0 rows exported
. exporting synonyms
EXP-00008: ORACLE error 904 encountered
ORA-00904: invalid column name
EXP-00000: Export terminated unsuccessfully
Could this be related to following code which is present in /oraclehome/rdbms/admin/catexp.sql
These are the last few lines of catexp.sql
REM Add versioning support for export
REM This will get bumped up as the views evolve. The insert is needed
REM for upgrades from 7.0 or new databases. The update is needed for
REM databases that have older compatibility.
REM These are the releases when the compatibility was bumped:
REM 7.0.* - no compatibility - assume zero
REM 7.1.3 - set to one
REM 7.2.1 - set to two
REM 7.2.3 - set to three
REM 8.0.1 - set to four
REM 8.0.2 - set to five
REM 8.0.3 - set to six
REM 8.0.4 - set to seven
REM
insert into props$
select 'EXPORT_VIEWS_VERSION', '7', 'Export views revision #' from dual
where not exists
(select 'x' from props$ where name = 'EXPORT_VIEWS_VERSION')
update props$ set value$ = 7 where name = 'EXPORT_VIEWS_VERSION'This forum is for feedback about the OTN program and problems with OTN accounts. Technical questions cannot be answered here. Please post your question in the appropriate product or technology forum. http://forums.oracle.com/forums/index.jsp?cat=48
-
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 RussellWe 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 -
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
Maybe you are looking for
-
New Windows 10 Insider Preview Build 10074 now available
New Windows 10 Insider Preview Build 10074 now available, see here- http://blogs.windows.com/bloggingwindows/2015/04/29/new-windows-10-insider-preview-build-10074-now-a... and from that page: New Windows 10 Insider Preview Build 10074 now available
-
Hi, I've just found my old iBook G4/1.33 12-Inch (Mid-2005 - Op) without the A/C Adapter and I would like to know if i can buy on generic A/C or if I need to respect the apple order N° of my iBook which is M9846LL/A. I've found an A/C but with the re
-
How do you adjust settings or is this not even possible with this new program?
I just loaded 4.1. How can you adjust settings with this new thing or is it not even possible? Like how can you adjust bitrate or do you have to use the templates as is?
-
Download von Updates für Photoshop CS
Jedesmal wenn ich den "Adobe DNG Converter and Camera Raw 2.4. Update" laden möchte, erhalte ich nach der Eingabe meiner Login-Daten nur die Fehlermeldung: "Es traten zu viele Verbindungswiederholungen beim Öffnen von http://www.adobe.com/support/dow
-
Where can I get the information
I need information on Java TAPI for doing VoIP connections. I can find posts asking about it, but can't find any actual Sun-related documentation. Any ideas?