CTM 8.5 Database Export issues
I am unable to complete a successful DB export using either the GUI or CLI procedures. When I do the CLI this is the messages I get. Any help would be appreciated, as I need to apply some patches.
TIA,
Steve.
# showctm
CTM Processes for
Cisco Transport Manager Server Version: 8.5 Build: 387 Patches: 6
USER PID %CPU %MEM START TIME PROCESS
root 3847 0.1 0.410457632904 14:31:10 0:21 CTM Server
root 3817 0.0 0.295200 14:31:05 0:00 CTM Server
root 4094 0.1 2.6413544208296 14:31:58 1:42 SnmpTrapService
root 3883 0.1 2.0395392162392 14:31:12 1:54 SMService
root 4125 4.1 11.01514856889232 14:31:59 40:19 CTC-based SONET NetworkService-4
root 3829 0.0 0.1 14:31:06 0:00 Apache Web Server
# pwd
/opt/CiscoTransportManagerServer/bin
# ./export_full_db.sh
Sun Microsystems Inc. SunOS 5.10 Generic January 2005
Export: Release 10.2.0.3.0 - Production on Fri Mar 25 14:56:20 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Release 10.2.0.3.0 - 64bit Production
Export done in US7ASCII character set and AL16UTF16 NCHAR character set
server uses UTF8 character set (possible charset conversion)
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
EXP-00008: ORACLE error 904 encountered
ORA-00904: "DBMS_JAVA"."LONGNAME": invalid identifier
EXP-00000: Export terminated unsuccessfully
Error in export full db, please check /oracle/admin/CTM/udump/export_db.log for details
# exporting: not foundEXP-00008: ORACLE error 904 encountered
# EXP-00008:: not found
ORA-00904: "DBMS_JAVA"."LONGNAME": invalid identifier
EXP-00000: Export terminated unsuccessfully# ORA-00904:: not found
Being new to CTM I wanted to make sure I posted this question in the appropriate forum. I looked around and thought this would be the most relevant, but I may be wrong. Does anyone know whether or not this is the appropriate forum for this question? If not, any suggestions on which one would be more appropriate?
Thanks
Similar Messages
-
StandBy database Create/Export Issue
We have database ABC and standby database ABCSTD and they are working properly. (Archives are properly applied), They were created from the database ABC_OLD.
Issue is that the ABC_OLD database has some more changes and users continued to work on that. We didnt switch the users to the ABC. And now the ABC database has become obsolete. its around one month old database.
I just want to know. Do I need to recreate the ABC database and Standby again from ABC_OLD cold backup Or Can I take full Database Export froom ABC_OLD and Import it on the the ABC Live.
Are there any other ways.??
Regards,
Rakesh Soni.Or Am i just overthinking on this?
Is dataguard only looking for the current and oldest log sequence? -
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 -
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 -
hi all
i need your help
i have completed my Database Migration from sql server 2008 to Oracle 11g
i got a very diffrent kind of issue:
Mgrated database
SQL SERVER 2008 to ORACLE 11g
using SQL DEVELOPER 3
and when completed with all compilation and cross check
i generated DATABASE Script
by
Database export Wizard
Format: insert
Line Terminator: enviroment default
Save :as single file
Encoding: Cp1252
<<<<what is the meaning of these attributes like format,encoding.....etc....>>>>>>>
and recreate in Oracle 11g,10g (on another machine)
where i got so many errors
most of time :
Error(48,13): PLS-00905: object DBO_PMS_DB.SQLSERVER_UTILITIES is invalid
SQLSERVER_UTILITIES is invalid
how to resolve this issue?
please help me out
thanks
Rajneeshh2. part 2
temp_exp := REPLACE(temp_exp, '()', '(1)');
IF TO_NUMBER(REGEXP_SUBSTR(temp_exp, '[[:digit:]]{2,4}$')) < 100 THEN
IF TO_NUMBER(REGEXP_SUBSTR(temp_exp, '[[:digit:]]{2,4}$')) > 50 THEN
temp_exp := REGEXP_REPLACE(temp_exp, '([[:digit:]]{2,4})$', '19' || '\1');
ELSE
temp_exp := REGEXP_REPLACE(temp_exp, '([[:digit:]]{2,4})$', '20' || '\1');
END IF;
END IF;
format_str := '(DD) MON YYYY';
ELSIF REGEXP_INSTR(temp_exp, '[-/\\.]') <> 0 THEN -- numeric date format
-- require the setting for SET FORMAT to determine the interpretation of the numeric date format,
-- default is mdy
IF REGEXP_INSTR(temp_exp,
-- e.g. 4/15/1996 or 15/4/1996 or 4/96/15
'^([[:digit:]]{1,2})[-/\.]([[:digit:]]{1,2})[-/\.]([[:digit:]]{2,4})$') = 1 THEN
temp_exp := REGEXP_REPLACE(temp_exp,
'^([[:digit:]]{1,2})[-/\.]([[:digit:]]{1,2})[-/\.]([[:digit:]]{2,4})$',
'\1/\2/\3');
ELSIF REGEXP_INSTR(temp_exp,
'^([[:digit:]]{1,2})[-/\.]([[:digit:]]{2,4})[-/\.]([[:digit:]]{1,2})$') = 1 THEN
-- e.g. 15/96/4
temp_exp := REGEXP_REPLACE(temp_exp,
'^([[:digit:]]{1,2})[-/\.]([[:digit:]]{2,4})[-/\.]([[:digit:]]{1,2})$',
'\1/\3/\2');
ELSIF REGEXP_INSTR(temp_exp,
'^([[:digit:]]{2,4})[-/\.]([[:digit:]]{1,2})[-/\.]([[:digit:]]{1,2})$') = 1 THEN
-- e.g. 1996/4/15 or 1996/15/4
temp_exp := REGEXP_REPLACE(temp_exp,
'^([[:digit:]]{2,4})[-/\.]([[:digit:]]{1,2})[-/\.]([[:digit:]]{1,2})$',
'\2/\3/\1');
END IF;
-- first component
temp_val := TO_NUMBER(SUBSTR(temp_exp, 1, INSTR(temp_exp, '/') - 1));
IF temp_val > 31 AND temp_val < 100 THEN
format_str := 'YYYY/';
IF temp_val > 50 THEN
temp_exp := '19' || temp_exp;
ELSE
temp_exp := '20' || temp_exp;
END IF;
ELSIF temp_val > 12 THEN
format_str := 'DD/';
ELSE
format_str := 'MM/';
END IF;
-- second component
temp_val := TO_NUMBER(SUBSTR(temp_exp, INSTR(temp_exp, '/') + 1, INSTR(temp_exp, '/', 1, 2) - INSTR(temp_exp, '/') - 1));
IF temp_val > 31 AND temp_val < 100 THEN
format_str := format_str || 'YYYY/';
IF temp_val > 50 THEN
temp_exp := REGEXP_REPLACE(temp_exp, '/([[:digit:]]{2,4})/', '/19' || '\1/');
ELSE
temp_exp := REGEXP_REPLACE(temp_exp, '/([[:digit:]]{2,4})/', '/20' || '\1/');
END IF;
ELSIF temp_val > 12 THEN
format_str := format_str || 'DD/';
ELSE
IF INSTR(format_str, 'MM') > 0 THEN
format_str := format_str || 'DD';
ELSE
format_str := format_str || 'MM/';
END IF;
END IF;
IF INSTR(format_str, 'MM') = 0 THEN
format_str := format_str || 'MM';
ELSIF INSTR(format_str, 'DD') = 0 THEN
format_str := format_str || 'DD';
ELSE
IF TO_NUMBER(REGEXP_SUBSTR(temp_exp, '[[:digit:]]{2,4}$')) < 100 THEN
IF TO_NUMBER(REGEXP_SUBSTR(temp_exp, '[[:digit:]]{2,4}$')) > 50 THEN
temp_exp := REGEXP_REPLACE(temp_exp, '([[:digit:]]{2,4})$', '19' || '\1');
ELSE
temp_exp := REGEXP_REPLACE(temp_exp, '([[:digit:]]{2,4})$', '20' || '\1');
END IF;
END IF;
format_str := format_str || '/YYYY';
END IF;
END IF;
END IF;
IF format_str IS NOT NULL THEN
RETURN TO_DATE(temp_exp, format_str);
ELSE
RETURN TO_DATE(temp_exp, 'DD-MON-YYYY HH24:MI:SS');
END IF;
EXCEPTION
WHEN OTHERS THEN
RETURN NULL;
END str_to_date;
FUNCTION convert_(p_dataType IN VARCHAR2, p_expr IN VARCHAR2, p_style IN VARCHAR2 DEFAULT NULL)
RETURN VARCHAR2
IS
v_ret_value VARCHAR2(50);
v_format VARCHAR2(30);
v_year_format VARCHAR2(5) := 'YY';
v_format_type NUMBER;
v_numeric_dataType BOOLEAN := TRUE;
v_is_valid_date BINARY_INTEGER := 0;
BEGIN
IF INSTR(UPPER(p_dataType), 'DATE') <> 0 OR INSTR(UPPER(p_dataType), 'CHAR') <> 0 OR
INSTR(UPPER(p_dataType), 'CLOB') <> 0 THEN
v_numeric_dataType := FALSE;
END IF;
IF NOT v_numeric_dataType THEN
SELECT NVL2(TO_DATE(p_expr), 1, 0) INTO v_is_valid_date FROM DUAL;
END IF;
IF (str_to_date(p_expr) IS NOT NULL OR v_is_valid_date != 0 ) THEN
IF p_style IS NULL THEN
v_ret_value := TO_NCHAR(p_expr);
ELSE -- convert date to character data
v_format_type := TO_NUMBER(p_style);
IF v_format_type > 100 THEN
v_year_format := 'YYYY';
END IF;
v_format := CASE
WHEN v_format_type = 1 OR v_format_type = 101 THEN 'MM/DD/' || v_year_format
WHEN v_format_type = 2 OR v_format_type = 102 THEN v_year_format || '.MM.DD'
WHEN v_format_type = 3 OR v_format_type = 103 THEN 'DD/MM/' || v_year_format
WHEN v_format_type = 4 OR v_format_type = 104 THEN 'DD.MM.' || v_year_format
WHEN v_format_type = 5 OR v_format_type = 105 THEN 'DD-MM-' || v_year_format
WHEN v_format_type = 6 OR v_format_type = 106 THEN 'DD MM ' || v_year_format
WHEN v_format_type = 7 OR v_format_type = 107 THEN 'MON DD, ' || v_year_format
WHEN v_format_type = 8 OR v_format_type = 108 THEN 'HH12:MI:SS'
WHEN v_format_type = 9 OR v_format_type = 109 THEN 'MON DD YYYY HH12:MI:SS.FF3AM'
WHEN v_format_type = 10 OR v_format_type = 110 THEN 'MM-DD-' || v_year_format
WHEN v_format_type = 11 OR v_format_type = 111 THEN v_year_format || '/MM/DD'
WHEN v_format_type = 12 OR v_format_type = 112 THEN v_year_format || 'MMDD'
WHEN v_format_type = 13 OR v_format_type = 113 THEN 'DD MON YYYY HH12:MI:SS.FF3'
WHEN v_format_type = 14 OR v_format_type = 114 THEN 'HH24:MI:SS.FF3'
WHEN v_format_type = 20 OR v_format_type = 120 THEN 'YYYY-MM-DD HH24:MI:SS'
WHEN v_format_type = 21 OR v_format_type = 121 THEN 'YYYY-MM-DD HH24:MI:SS.FF3'
WHEN v_format_type = 126 THEN 'YYYY-MM-DD HH12:MI:SS.FF3'
WHEN v_format_type = 127 THEN 'YYYY-MM-DD HH12:MI:SS.FF3'
WHEN v_format_type = 130 THEN 'DD MON YYYY HH12:MI:SS:FF3AM'
WHEN v_format_type = 131 THEN 'DD/MM/YY HH12:MI:SS:FF3AM'
END;
v_ret_value := CASE
WHEN v_format_type = 9 OR v_format_type = 109 OR
v_format_type = 13 OR v_format_type = 113 OR
v_format_type = 14 OR v_format_type = 114 OR
v_format_type = 20 OR v_format_type = 120 OR
v_format_type = 21 OR v_format_type = 121 OR
v_format_type = 126 OR v_format_type = 127 OR
v_format_type = 130 OR v_format_type = 131 THEN
CASE UPPER(p_dataType)
WHEN 'DATE' THEN TO_CHAR(TO_TIMESTAMP(p_expr, v_format))
ELSE TO_CHAR(TO_TIMESTAMP(p_expr), v_format)
END
ELSE
CASE UPPER(p_dataType)
WHEN 'DATE' THEN TO_CHAR(TO_DATE(p_expr, v_format))
ELSE TO_CHAR(TO_DATE(p_expr), v_format)
END
END;
END IF;
ELSE
-- convert money or smallmoney to character data
IF SUBSTR(p_expr, 1, 1) = '$' THEN
v_ret_value := CASE TO_NUMBER(NVL(p_style, 1))
WHEN 1 THEN TO_CHAR(SUBSTR(p_expr, 2), '999999999999999990.00')
WHEN 2 THEN TO_CHAR(SUBSTR(p_expr, 2), '999,999,999,999,999,990.00')
WHEN 3 THEN TO_CHAR(SUBSTR(p_expr, 2), '999999999999999990.0000')
END;
ELSE -- convert numeric data to character data
v_ret_value := TO_CHAR(p_expr);
END IF;
END IF;
RETURN v_ret_value;
EXCEPTION
WHEN OTHERS THEN
raise_application_error(-20000, DBMS_UTILITY.FORMAT_ERROR_STACK);
END convert_;
FUNCTION year_(p_date_str IN VARCHAR2)
RETURN NUMBER
IS
v_date DATE;
BEGIN
v_date := str_to_date(p_date_str);
IF v_date IS NULL THEN
RETURN NULL;
END IF;
RETURN TO_NUMBER(TO_CHAR(v_date, 'YY'));
EXCEPTION
WHEN OTHERS THEN
raise_application_error(-20000, DBMS_UTILITY.FORMAT_ERROR_STACK);
END year_;
FUNCTION stuff(p_expr VARCHAR2, p_startIdx NUMBER, p_len NUMBER, p_replace_expr VARCHAR2)
RETURN VARCHAR2
IS
BEGIN
RETURN REPLACE(p_expr, SUBSTR(p_expr, p_startIdx, p_len), p_replace_expr);
EXCEPTION
WHEN OTHERS THEN
raise_application_error(-20000, DBMS_UTILITY.FORMAT_ERROR_STACK);
END stuff;
PROCEDURE incrementTrancount
IS
BEGIN
trancount := trancount + 1;
END incrementTrancount;
FUNCTION dateadd(p_interval IN VARCHAR2, p_interval_val IN NUMBER, p_date_str IN VARCHAR2)
RETURN DATE
IS
v_ucase_interval VARCHAR2(10);
v_date DATE;
BEGIN
v_date := str_to_date(p_date_str);
v_ucase_interval := UPPER(p_interval);
IF v_ucase_interval IN ('YEAR', 'YY', 'YYYY')
THEN
RETURN ADD_MONTHS(v_date, p_interval_val * 12);
ELSIF v_ucase_interval IN ('QUARTER', 'QQ', 'Q')
THEN
RETURN ADD_MONTHS(v_date, p_interval_val * 3);
ELSIF v_ucase_interval IN ('MONTH', 'MM', 'M')
THEN
RETURN ADD_MONTHS(v_date, p_interval_val);
ElSIF v_ucase_interval IN ('DAYOFYEAR', 'DY', 'Y', 'DAY', 'DD', 'D', 'WEEKDAY', 'DW', 'W')
THEN
RETURN v_date + p_interval_val;
ElSIF v_ucase_interval IN ('WEEK', 'WK', 'WW')
THEN
RETURN v_date + (p_interval_val * 7);
ElSIF v_ucase_interval IN ('HOUR', 'HH')
THEN
RETURN v_date + (p_interval_val / 24);
ElSIF v_ucase_interval IN ('MINUTE', 'MI', 'N')
THEN
RETURN v_date + (p_interval_val / 24 / 60);
ElSIF v_ucase_interval IN ('SECOND', 'SS', 'S')
THEN
RETURN v_date + (p_interval_val / 24 / 60 / 60);
ElSIF v_ucase_interval IN ('MILLISECOND', 'MS')
THEN
RETURN v_date + (p_interval_val / 24 / 60 / 60 / 1000);
ELSE
RETURN NULL;
END IF;
EXCEPTION
WHEN OTHERS THEN
raise_application_error(-20000, DBMS_UTILITY.FORMAT_ERROR_STACK);
END dateadd;
FUNCTION isdate(p_expr IN VARCHAR2)
RETURN NUMBER
IS
v_is_valid_date BINARY_INTEGER := 0;
BEGIN
IF str_to_date(p_expr) IS NOT NULL THEN
RETURN 1;
ELSE
SELECT NVL2(TO_DATE(p_expr), 1, 0) INTO v_is_valid_date FROM DUAL;
RETURN v_is_valid_date;
END IF;
EXCEPTION
WHEN OTHERS THEN
RETURN 0;
END isdate;
FUNCTION stats_date(p_table IN VARCHAR2, p_index IN VARCHAR2)
RETURN DATE
IS
v_last_analyzed DATE;
BEGIN
SELECT last_analyzed INTO v_last_analyzed
FROM USER_IND_STATISTICS
WHERE table_name LIKE UPPER(p_table)
AND index_name LIKE UPPER(p_index);
RETURN v_last_analyzed;
EXCEPTION
WHEN OTHERS THEN
raise_application_error(-20000, DBMS_UTILITY.FORMAT_ERROR_STACK);
END stats_date;
FUNCTION rand(p_seed NUMBER DEFAULT NULL)
RETURN NUMBER
IS
v_rand_num NUMBER;
BEGIN
IF p_seed IS NOT NULL THEN
DBMS_RANDOM.SEED(p_seed);
END IF;
v_rand_num := DBMS_RANDOM.VALUE();
RETURN v_rand_num;
EXCEPTION
WHEN OTHERS THEN
raise_application_error(-20000, DBMS_UTILITY.FORMAT_ERROR_STACK);
END rand;
FUNCTION to_base(p_dec NUMBER, p_base NUMBER)
RETURN VARCHAR2
IS
v_str VARCHAR2(255);
v_num NUMBER;
v_hex VARCHAR2(16) DEFAULT '0123456789ABCDEF';
BEGIN
v_num := p_dec;
IF p_dec IS NULL OR p_base IS NULL THEN
RETURN NULL;
END IF;
IF TRUNC(p_dec) <> p_dec OR p_dec < 0 THEN
RAISE PROGRAM_ERROR;
END IF;
LOOP
v_str := SUBSTR(v_hex, MOD(v_num, p_base) + 1, 1) || v_str;
v_num := TRUNC(v_num / p_base);
EXIT WHEN v_num = 0;
END LOOP;
RETURN v_str;
EXCEPTION
WHEN OTHERS THEN
raise_application_error(-20000, DBMS_UTILITY.FORMAT_ERROR_STACK);
END to_base;
FUNCTION patindex(p_pattern IN VARCHAR2, p_expr IN VARCHAR2)
RETURN NUMBER
IS
v_search_pattern VARCHAR2(100);
v_pos NUMBER := 0;
BEGIN
IF p_pattern IS NULL OR p_expr IS NULL THEN
RETURN NULL;
END IF;
IF NOT DBMS_DB_VERSION.VER_LE_9_2 THEN
v_search_pattern := p_pattern;
v_search_pattern := REPLACE(v_search_pattern, '\', '\\');
v_search_pattern := REPLACE(v_search_pattern, '*', '\*');
v_search_pattern := REPLACE(v_search_pattern, '+', '\+');
v_search_pattern := REPLACE(v_search_pattern, '?', '\?');
v_search_pattern := REPLACE(v_search_pattern, '|', '\|');
v_search_pattern := REPLACE(v_search_pattern, '^', '\^');
v_search_pattern := REPLACE(v_search_pattern, '$', '\$');
v_search_pattern := REPLACE(v_search_pattern, '.', '\.');
v_search_pattern := REPLACE(v_search_pattern, '{', '\{');
v_search_pattern := REPLACE(v_search_pattern, '_', '.');
IF SUBSTR(v_search_pattern, 1, 1) != '%' AND
SUBSTR(v_search_pattern, -1, 1) != '%' THEN
v_search_pattern := '^' || v_search_pattern || '$';
ELSIF SUBSTR(v_search_pattern, 1, 1) != '%' THEN
v_search_pattern := '^' || SUBSTR(v_search_pattern, 1, LENGTH(v_search_pattern) - 1);
ELSIF SUBSTR(v_search_pattern, -1, 1) != '%' THEN
v_search_pattern := SUBSTR(v_search_pattern, 2) || '$';
ELSE
v_search_pattern := SUBSTR(v_search_pattern, 2, LENGTH(v_search_pattern) - 2);
END IF;
v_pos := REGEXP_INSTR(p_expr, v_search_pattern);
ELSE
v_pos := 0;
END IF;
RETURN v_pos;
EXCEPTION
WHEN OTHERS THEN
raise_application_error(-20000, DBMS_UTILITY.FORMAT_ERROR_STACK);
END patindex;
FUNCTION datediff(p_datepart VARCHAR2, p_start_date_str VARCHAR2, p_end_date_str VARCHAR2)
RETURN NUMBER
IS
v_ret_value NUMBER := NULL;
v_part VARCHAR2(15);
v_start_date DATE;
v_end_date DATE;
BEGIN
v_start_date := str_to_date(p_start_date_str);
v_end_date := str_to_date(p_end_date_str);
v_part := UPPER(p_datepart);
IF v_part IN ('YEAR', 'YY', 'YYYY') THEN
IF EXTRACT(YEAR FROM v_end_date) - EXTRACT(YEAR FROM v_start_date) = 1 AND
EXTRACT(MONTH FROM v_start_date) = 12 AND EXTRACT(MONTH FROM v_end_date) = 1 AND
EXTRACT(DAY FROM v_start_date) = 31 AND EXTRACT(DAY FROM v_end_date) = 1 THEN
-- When comparing December 31 to January 1 of the immediately succeeding year,
-- DateDiff for Year ("yyyy") returns 1, even though only a day has elapsed.
v_ret_value := 1;
ELSE
v_ret_value := ROUND(MONTHS_BETWEEN(v_end_date, v_start_date) / 12);
END IF;
ELSIF v_part IN ('QUARTER', 'QQ', 'Q') THEN
v_ret_value := ROUND(MONTHS_BETWEEN(v_end_date, v_start_date) / 3);
ELSIF v_part IN ('MONTH', 'MM', 'M') THEN
v_ret_value := ROUND(MONTHS_BETWEEN(v_end_date, v_start_date));
ElSIF v_part IN ('DAYOFYEAR', 'DY', 'Y') THEN
v_ret_value := ROUND(v_end_date - v_start_date);
ElSIF v_part IN ('DAY', 'DD', 'D') THEN
v_ret_value := ROUND(v_end_date - v_start_date);
ElSIF v_part IN ('WEEK', 'WK', 'WW') THEN
v_ret_value := ROUND((v_end_date - v_start_date) / 7);
ELSIF v_part IN ('WEEKDAY', 'DW', 'W') THEN
v_ret_value := TO_CHAR(v_end_date, 'D') - TO_CHAR(v_start_date, 'D');
ElSIF v_part IN ('HOUR', 'HH') THEN
v_ret_value := ROUND((v_end_date - v_start_date) * 24);
ElSIF v_part IN ('MINUTE', 'MI', 'N') THEN
v_ret_value := ROUND((v_end_date - v_start_date) * 24 * 60);
ElSIF v_part IN ('SECOND', 'SS', 'S') THEN
v_ret_value := ROUND((v_end_date - v_start_date) * 24 * 60 * 60);
ElSIF v_part IN ('MILLISECOND', 'MS') THEN
v_ret_value := ROUND((v_end_date - v_start_date) * 24 * 60 * 60 * 1000);
END IF;
RETURN v_ret_value;
EXCEPTION
WHEN OTHERS THEN
raise_application_error(-20000, DBMS_UTILITY.FORMAT_ERROR_STACK);
END datediff;
FUNCTION day_(p_date_str IN VARCHAR2)
RETURN NUMBER
IS
v_date DATE;
BEGIN
v_date := str_to_date(p_date_str);
IF v_date IS NULL THEN
RETURN NULL;
END IF;
RETURN TO_NUMBER(TO_CHAR(v_date, 'DD'));
EXCEPTION
WHEN OTHERS THEN
raise_application_error(-20000, DBMS_UTILITY.FORMAT_ERROR_STACK);
END day_;
FUNCTION ident_incr(p_sequence IN VARCHAR2)
RETURN NUMBER
IS
v_incr_by NUMBER;
BEGIN
SELECT increment_by INTO v_incr_by
FROM USER_SEQUENCES
WHERE sequence_name LIKE UPPER(p_sequence);
RETURN v_incr_by;
EXCEPTION
WHEN OTHERS THEN
raise_application_error(-20000, DBMS_UTILITY.FORMAT_ERROR_STACK);
END ident_incr;
FUNCTION isnumeric(p_expr IN VARCHAR2)
RETURN NUMBER
IS
numeric_val NUMBER;
temp_str VARCHAR2(50);
BEGIN
temp_str := p_expr;
IF SUBSTR(temp_str, 1, 1) = '$' THEN
temp_str := SUBSTR(temp_str, 2);
END IF; -
I was wondering if I'm simply not getting this right or there is something I'm missing. When I use the Database Export tool and select Export DDL including the check job for grants and no data when I get the ddl back it has the sql to create the table but the sql for the grants is not in the text. I know the table has grants because I can see them in the on the table when I highlight the table. I have noticed the same behavior with materialized view in the ddl is created but the grants statements are not provided. Just wondering if I missing something or should the grant statements be generated.
Thanks,For the pre-10g standard exp and imp utilities the answer is NO sys issued grants on sys owned objects are not exported. Grants are associated with the object being exported. By default when you export a table the grants on that table are also exported and on import Oracle will reissue each grant on the object. You get a nice list of errors for grants to users who do not exist in the new environment. Since SYS owned objects are not exported neighter are the grants.
It is very easy to generate a list of the SYS owned ojbects grants not provided by Oracle and reapply the grants on the target system.
The same is probably true with expdp but I cannot be 100% certain without checking my manual since I have not ran enough impdp tasks to verify that there has been no change in behavior. But I do not expect to find a change.
HTH -- Mark D Powell -- -
Clarification: by textbox -- I mean a "text" shape created by using the "A Text" tool that appears in the ribbon. They are just free text boxes that are not associated w/
any other shape.
Hi. I am using Visio Professional 2010. I am interested in extracting from each of my visio diagrams/drawings the text information that is shown in textboxes.
I've tried using the Database Export Wizard and the Reports add-on; neither work. I've tried exporting to Excel and to Access.
What I end up w/ is for some textboxes, the contained text is exported. But for other textboxes, nothing is exported or in some cases just a single letter/character is exported. I checked the number of characters in each textbox and all but one have fewer
than 255 characters -- (if that makes a difference??). Some textboxes contain newline character (i.e., carriage returns). Does that make a difference?
I've looked at previous questions and answers on the web and on this forum re. this topic and followed the proscribed advice, w/ no success. So any additional advice anyone can provide me, I would greatly appreciate it.
Thanks -
CJAHey Chris,
I tried exporting the text in visio drawing using database export wizard and found that yes the text which is associated with the sub group doesn't get exported.
So the solution I think would work is that we have to write a macro which would read the shape.text property and it should check that if the shape is a group shape then it would check the sub shapes to get the text associated with them.
You can refer to following msdn page to write this macro,
msdn.microsoft.com/en-us/library/office/ff766497(v=office.15).aspx
Let me know if you need further help to resolve your issue or if I have missed something. -
Database export/exports are extremely slow
We run PeopleSoft (PeopleTools version 8.46) applications on Oracle 10g (10.1.0.3). database exports/imports were extremely slow, so when we contact PeopleSoft customer connection, we were advised to modify the init.ora file with the "_optimizer_cost_based_transformation=off". After we set the init.ora file, exports/imports are very fast.
What is optimizercost_based_transformation? will database performance have any effect by setting this parameter? Does anybody has issues with 10g export/import issues?
any help?
Thanks,Here is the extract from PeopleSoft customer connection -
. Required INIT.ORA Parameters for Oracle 10g
. Change #1 - optimizercost_based_transformation=off
According to Oracle support: "This parameter controls whether query transformations (sub-query unnesting, complex view merging and push join predicate ) are performed using an algorithm that relies only on optimizer cost (new in 10g) or an algorithm that uses a combination of optimizer cost and heuristics (pre-10g). "
Can anbody tell me how extaclty this parameter will affect the performance of the system? Althoght we didn't see any performance issues right now (We are just in the process of implimentaion) Going forward, i am worried to have this im my init.ora file.
Any thoughts/suggestions related to this topic is helpful.
THanks, -
Urgent help needed; Database shutdown issues.
Urgent help needed; Database shutdown issues.
Hi all,
I am trying to shutdown my SAP database and am facing the issues below, can someone please suggest how I can go about resolving this issue and restart the database?
SQL> shutdown immediate
ORA-24324: service handle not initialized
ORA-24323: value not allowed
ORA-01089: immediate shutdown in progress - no operations are permitted
SQL> shutdown abort
ORA-01031: insufficient privileges
Thanks and regards,
IqbalHi,
check SAP Note 700548 - FAQ: Oracle authorizations
also check Note 834917 - Oracle Database 10g: New database role SAPCONN
regards,
kaushal -
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!!!! -
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 bug issue after upgrade ( version 8.1.7.4)
Hi,
Currently our database version is 8.1.7.0.0
We have planned to upgrade our database to 10g Rel2 and for that we have already applied terminal patch set (i.e. 8.1.7.4).
But after applying terminal patch set we came through list of the GENERIC bug fixes included in the 817X Patch Sets. i.e.
ALERT: Oracle8i Release 3 (8.1.7) Support Status and Alerts
Note :- 120607.1
Actually in this note we are having confusion whether to apply the patch or not for the bug that is mentioned.
Some are those which affect Oracle 8.1.7.X releases are :
1)Trigger updates wrong after DROP functional index Note 259854.1
2)Changing the Database Character Set can corrupt LOBs Note 118242.1
3)Large export buffer can produce corrupt export file Note 223399.1
4)Export can generate a corrupt export file Note 199416.1
The first one has been applied successully, but having confusion with the remaining,
Question regarding points 2 & 3 above :
2)
As we are not going to alter our database character set (WE8ISO8859P1) at 8.1.7.4, so is it required to apply the patch ???
or will have to apply as we are going to upgrade it further to 10g Rel2(Here database character set might get change) for future upgradation ???
3)
Currently our database export is being done via conventional path
Now, the workaround mentioned in the patch is as follows :
(Patch is not available for Windows OS)
Workaround
~~~~~~~~~~
1. Prior to a Conventional path export, set the environment variable
ORA_OCI_NO_OPTIMIZED_FETCH to 1.
Windows:
set ORA_OCI_NO_OPTIMIZED_FETCH=1
OR:
2. Export the data in Direct path mode, by specifiying the additional
export parameter: DIRECT=Y
So the query is,
I am not getting any parameter like ORA_OCI_NO_OPTIMIZED_FETCH.
Is there any parameter like ORA_OCI_NO_OPTIMIZED_FETCH in oracle 8.1.7.4 ?
OR
Will have to change the export method to direct mode ? by doing so will there be any adverse effect ?
With RegardsYou are repeating a question that you already made on your previous thread.
Re: Database upgradation to 9i rel2
Regards,
Francisco Munoz Alvarez
www.oraclenz.com -
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?
Maybe you are looking for
-
PDF files doesn't open automatically anymore why ?
Hi, Everytime I clic on a PDF files, it open my adobe acrobat pro software but not the file in it, then I have to open my file in the software, before it was automatic, someone knows why ? I looked in the setting and preferences and found nothing who
-
Repeat all events of a calendar
Hi there, Does anybody know a way to set all events of a calendar to get repeated every year? (With the help of apple script or sth. else??) Thanks
-
Will audition 1.5 work on windows 8?
has anyone ever used auditon 1.5?
-
Hi, I am working on Discrete Jobs Open interface (WIP MASS LOAD). How to associate Sales to a Discrete Job using Discrete Job Open Interface. I am able to create jobs by loading information into WIP_JOB_SCHEDULE_INTERFACE table. But, i want to associ
-
Dear Reader I have forgotten the answers to my security-questions. So it says that i will get an e-mail to reset my questions, but i have not gotten an e-mail? So i tried it again (after a month) and it still doesen't work. I really need to know what