Failed to track ddl statements
Hi
We are using oracle 9.2.0 database and set up logminer in order to track ddl and dml changes but
returning previous data i mean latest archived archive logfile " ARC00140.001" but it showing the previous archive log file when
query the below dictionay view
SQL> select name from v$archived_log where dictionary_begin='YES';
NAME
D:\ORACLE\ORA92\RDBMS\ARCH\ARC00007.001
SQL> select name from v$archived_log where dictionary_end='YES'
2 ;
NAME
D:\ORACLE\ORA92\RDBMS\ARCH\ARC00007.001
And done some modifications in scott schema and issued
alter system switch log file 15 or 20 times and follwed the follwing steps to setup logminer
set utl_file_dir='d:\oracle' in spfile using scope option
SQL> ALTER DATABASE ADD SUPPLEMENTAL LOG DATA
sql> exec dbms_logmnr_d.build('dict.ora','d:\oracle')
SQL> exec dbms_logmnr.add_logfile(logfilename=>'D:\ORACLE\ORA92\RDBMS\ARCH\AR
117.001', options=>dbms_logmnr.new);
PL/SQL procedure successfully completed.
SQL> exec dbms_logmnr.add_logfile(logfilename=>'D:\ORACLE\ORA92\RDBMS\ARCH\AR
118.001', options=>dbms_logmnr.new);
PL/SQL procedure successfully completed.
SQL> exec dbms_logmnr.add_logfile(logfilename=>'D:\ORACLE\ORA92\RDBMS\ARCH\AR
119.001', options=>dbms_logmnr.new);
PL/SQL procedure successfully completed.
SQL> exec dbms_logmnr.add_logfile(logfilename=>'D:\ORACLE\ORA92\RDBMS\ARCH\AR
120.001', options=>dbms_logmnr.new);
PL/SQL procedure successfully completed.
SQL> exec dbms_logmnr.add_logfile(logfilename=>'D:\ORACLE\ORA92\RDBMS\ARCH\AR
121.001', options=>dbms_logmnr.new);
PL/SQL procedure successfully completed.
SQL> exec dbms_logmnr.add_logfile(logfilename=>'D:\ORACLE\ORA92\RDBMS\ARCH\AR
122.001', options=>dbms_logmnr.new);
PL/SQL procedure successfully completed.
SQL> exec dbms_logmnr.add_logfile(logfilename=>'D:\ORACLE\ORA92\RDBMS\ARCH\AR
123.001', options=>dbms_logmnr.new);
PL/SQL procedure successfully completed.
SQL> exec dbms_logmnr.start_logmnr(dictfilename=>'d:\oracle\z.ora',options => -
DBMS_LOGMNR.DDL_DICT_TRACKING);
PL/SQL procedure successfully completed.
SQL> select count(*) from v$logmnr_contents;
COUNT(*)
0
Thnaks inadvance
Mohan
Hi
We are using oracle 9.2.0 database and set up logminer in order to track ddl and dml changes but
returning previous data i mean latest archived archive logfile " ARC00140.001" but it showing the previous archive log file when
query the below dictionay view
SQL> select name from v$archived_log where dictionary_begin='YES';
NAME
D:\ORACLE\ORA92\RDBMS\ARCH\ARC00007.001
SQL> select name from v$archived_log where dictionary_end='YES'
2 ;
NAME
D:\ORACLE\ORA92\RDBMS\ARCH\ARC00007.001
And done some modifications in scott schema and issued
alter system switch log file 15 or 20 times and follwed the follwing steps to setup logminer
set utl_file_dir='d:\oracle' in spfile using scope option
SQL> ALTER DATABASE ADD SUPPLEMENTAL LOG DATA
sql> exec dbms_logmnr_d.build('dict.ora','d:\oracle')
SQL> exec dbms_logmnr.add_logfile(logfilename=>'D:\ORACLE\ORA92\RDBMS\ARCH\AR
117.001', options=>dbms_logmnr.new);
PL/SQL procedure successfully completed.
SQL> exec dbms_logmnr.add_logfile(logfilename=>'D:\ORACLE\ORA92\RDBMS\ARCH\AR
118.001', options=>dbms_logmnr.new);
PL/SQL procedure successfully completed.
SQL> exec dbms_logmnr.add_logfile(logfilename=>'D:\ORACLE\ORA92\RDBMS\ARCH\AR
119.001', options=>dbms_logmnr.new);
PL/SQL procedure successfully completed.
SQL> exec dbms_logmnr.add_logfile(logfilename=>'D:\ORACLE\ORA92\RDBMS\ARCH\AR
120.001', options=>dbms_logmnr.new);
PL/SQL procedure successfully completed.
SQL> exec dbms_logmnr.add_logfile(logfilename=>'D:\ORACLE\ORA92\RDBMS\ARCH\AR
121.001', options=>dbms_logmnr.new);
PL/SQL procedure successfully completed.
SQL> exec dbms_logmnr.add_logfile(logfilename=>'D:\ORACLE\ORA92\RDBMS\ARCH\AR
122.001', options=>dbms_logmnr.new);
PL/SQL procedure successfully completed.
SQL> exec dbms_logmnr.add_logfile(logfilename=>'D:\ORACLE\ORA92\RDBMS\ARCH\AR
123.001', options=>dbms_logmnr.new);
PL/SQL procedure successfully completed.
SQL> exec dbms_logmnr.start_logmnr(dictfilename=>'d:\oracle\z.ora',options => -
DBMS_LOGMNR.DDL_DICT_TRACKING);
PL/SQL procedure successfully completed.
SQL> select count(*) from v$logmnr_contents;
COUNT(*)
0
Thnaks inadvance
Mohan
Similar Messages
-
Hi all
I want to track all DDL statements fiered on the database like Drop, Alter, Truncate, Create.
I tried looking in metalink and found out that I have to right a trigger for it.
but couldn't find any script for it.
Can anyone help me with this.Writing triggers would be one way. The other ways is to enabling DDL auditing. Refer oracle docs. also search in this forum or http://www.asktom.oracle.com site.
Jaffar -
Track DDL statements for schema.
Dear all,
I want to track all DDL statements being performed on particular schema.
I want to capture entire sql statement being run.
How can I achive this.
Please advice.
Waiting for your reply.
Regards,Hi all,
I have used this trigger to track ddl.
create table perfstat.stats$ddl_log(
user_name varchar2(30),
ddl_date date,
ddl_type varchar2(30),
object_type varchar2(18),
owner varchar2(30),
object_name varchar2(128)
create or replace triggerDDLTrigger
AFTER DDL ON DATABASE
BEGIN
insert into
perfstat.stats$ddl_log
user_name,
ddl_date,
ddl_type,
object_type,
owner,
object_name
VALUES
ora_login_user,
sysdate,
ora_sysevent,
ora_dict_obj_type,
ora_dict_obj_owner,
ora_dict_obj_name
END;
It's working fine ,
But I want to capture entire sql statement into stats$ddl_log table.
What to modify in table or trigger that I could achive this.
Waiting for your reply.
Thanks and regards... -
"DDL statement failed" in Database load faze
Hello,
I have an problem when installing DB2 on Solaris platform.
During the installation, in Database load Faze, i get the error:
MSC-01015 Process finished with error(s), check log file /tmp/sapinst_instdir/R3E47X2/SYSTEM/ABAP/DB6/NUC/DB/SAPVIEW.log
I check the log & it has a whole bunch on tables that are created & at the end of it i get this message:
DB) ERROR: DDL statement failed
(CREATE VIEW "D010TINF" ( "PROG", "R3STATE", "LANGUAGE", "UNAM", "UDAT", "UTIME", "DATALG" ) AS SELECT T0001."PROGNAME"
, T0001."R3STATE", T0001."LANGUAGE", T0001."UNAM", T0001."UDAT", T0001."UTIME", T0001."DATALG" FROM "REPOTEXT" T0001)
DbSlExecute: rc = 103
(SQL error -204)
error message returned by DbSl:
SQL0204N "SAPS47.REPOTEXT"; is an undefined name. SQLSTATE=42704
(DB) INFO: disconnected from DB
/sapmnt/S47/exe/R3load: job finished with 1 error(s)
/sapmnt/S47/exe/R3load: END OF LOG: 20080810125355
/sapmnt/S47/exe/R3load: START OF LOG: 20080810130455
/sapmnt/S47/exe/R3load: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP
/sapmnt/S47/exe/R3load: version R6.40/V1.4
/sapmnt/S47/exe/R3load -dbcodepage 1100 -i /tmp/sapinst_instdir/R3E47X2/SYSTEM/ABAP/DB6/NUC/DB/SAPVIEW.cmd -l /tmp/sapin
st_instdir/R3E47X2/SYSTEM/ABAP/DB6/NUC/DB/SAPVIEW.log -c 300 -merge_bck -stop_on_error
(DB) INFO: connected to DB
(DB) ERROR: DDL statement failed
(DROP VIEW "D010TINF")
DbSlExecute: rc = 103
(SQL error -204)
error message returned by DbSl:
SQL0204N "SAPS47.D010TINF"; is an undefined name. SQLSTATE=42704
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
(CREATE VIEW "D010TINF" ( "PROG", "R3STATE", "LANGUAGE", "UNAM", "UDAT", "UTIME", "DATALG" ) AS SELECT T0001."PROGNAME"
, T0001."R3STATE", T0001."LANGUAGE", T0001."UNAM", T0001."UDAT", T0001."UTIME", T0001."DATALG" FROM "REPOTEXT" T0001)
DbSlExecute: rc = 103
(SQL error -204)
error message returned by DbSl:
SQL0204N "SAPS47.REPOTEXT"; is an undefined name. SQLSTATE=42704
(DB) INFO: disconnected from DB
/sapmnt/S47/exe/R3load: job finished with 1 error(s)
/sapmnt/S47/exe/R3load: END OF LOG: 20080810130457
/sapmnt/S47/exe/R3load: START OF LOG: 20080810140953
/sapmnt/S47/exe/R3load: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP
/sapmnt/S47/exe/R3load: version R6.40/V1.4
/sapmnt/S47/exe/R3load -dbcodepage 1100 -i /tmp/sapinst_instdir/R3E47X2/SYSTEM/ABAP/DB6/NUC/DB/SAPVIEW.cmd -l /tmp/sapin
st_instdir/R3E47X2/SYSTEM/ABAP/DB6/NUC/DB/SAPVIEW.log -c 300 -merge_bck -stop_on_error
(DB) INFO: connected to DB
(DB) ERROR: DDL statement failed
(DROP VIEW "D010TINF")
DbSlExecute: rc = 103
(SQL error -204)
error message returned by DbSl:
SQL0204N "SAPS47.D010TINF"; is an undefined name. SQLSTATE=42704
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
(CREATE VIEW "D010TINF" ( "PROG", "R3STATE", "LANGUAGE", "UNAM", "UDAT", "UTIME", "DATALG" ) AS SELECT T0001."PROGNAME"
, T0001."R3STATE", T0001."LANGUAGE", T0001."UNAM", T0001."UDAT", T0001."UTIME", T0001."DATALG" FROM "REPOTEXT" T0001)
DbSlExecute: rc = 103
(SQL error -204)
error message returned by DbSl:
SQL0204N "SAPS47.REPOTEXT"; is an undefined name. SQLSTATE=42704
(DB) INFO: disconnected from DB
/sapmnt/S47/exe/R3load: job finished with 1 error(s)
/sapmnt/S47/exe/R3load: END OF LOG: 20080810140954
Please lend me some of your wisdom
Regards,
Yoav ZilbermanHi Yoav,
your import failed already before the SAPVIEW package was processed. You should check the other packages too for errors or for packages which are not imported. But the errors show that at lease the tables REPOTEXT and D010TINF are missing. I'm not sure, but I think they are in SAPDDIC package. You should run the package again before running SAPVIEW. For a functioning system you need both, tables and views.
Regards
Ralph -
ERROR exec_ddl_stmt: (DB) ERROR: DDL statement failed during migration.
Hello Experts ,
We are in process of migration and after 90% of migration we are getting the following error as mentioned in MIGRATE_DT_XXXXX_IMP.log.:
ERROR exec_ddl_stmt: (DB) ERROR: DDL statement failed
( ALTER TABLE "EDID4" ADD PRIMARY KEY( "MANDT" , "DOCNUM" , "COUNTER" , "SEGNUM" ))
DbSlExecute: rc = 99
(SQL error -10108)
error message returned by DbSl:
ERROR exec_ddl_stmt: (DB) ERROR: DDL statement failed
( ALTER TABLE "EDID4" enable persistent merge )
DbSlExecute: rc = 99
(SQL error 131)
error message returned by DbSl:
transaction rolled back by lock wait timeout: Lock timeout occurs while waiting TABLE_LOCK of mode EXCLUSIVE(TRANSACTION_ID=14, UPDATE_TRANSACTION_ID=1442668)
(DB) INFO: disconnected from DB
I ran r3tans -d too to check the connection but it shows "Disconnected from DB".
Can someone please let me know what went wrong.
Environment Details :
SOurce : ECC 6 Ehp5 NW702 Oracle10
Target : ECC 6 Ehp7 NW740 HANA 1.0 Rev85
Tool : SUM 1.0 SP12 PL04
Phase Name :
MAIN_SWITCH/SUBMOD_MIG_SWITCH/SUBMOD_MIG_DOWNTIME_RUN/EU_CLONE_MIG_DT_RUN
Thanks
DevHi, Check the Blog - DMO: optimizing system downtime ...
we already had a discussion about in another request.
Best Regards Roland -
ABAP Import Phase DDL Statement Error
Hi Experts!
I am installing SAP Netweaver PI 7.3 EHP1 and encountered an error in the ABAP import phase.
I checked the import monitor logs and found a clue about SAPVIEW.log.
I have checked the SAPVIEW.log and found out the following:
ERROR: DDL statement failed
( DROP VIEW "APPL_MODS" )
dsql_exec_immediate returned DS_DBOBJECTUNKNOWN
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
( CREATE VIEW "APPL_MODS" ( "NAME", "TYP", "MEMBER", "DEVCLASS" ) AS SELECT T0001."NAME", T0001."TYP", T0001."MEMBER", T0002."DEVCLASS" FROM "MODSAP" T0001, "MODSAPA" T0002 WHERE T0001."NAME" = T0002."NAME" AND T0002."MIGRATED" <> 'X' )
dsql_exec_immediate returned DS_DBOBJECTUNKNOWN
(DB) INFO: disconnected from DB
/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: job finished with 1 error(s)
/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: END OF LOG:
Please help!
Also please let me know if any further detail is required.
Regards,
AyanGaurav,
Please find the below pasted trace from SAPVIEW.log
/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: START OF LOG: 20140823014048
/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: sccsid @(#) $Id: //bas/721_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: version R7.20/V1.6 [UNICODE]
Compiled Dec 4 2013 12:54:08
/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load -ctf I /backup/NW7.3_EHP1/ABAP_Inst_EXP/51043228/DATA_UNITS/EXP3/DATA/SAPVIEW.STR /tmp/sapinst_instdir/NW731/DB6/INSTALL/STD/AS/DDLDB6.TPL SAPVIEW.TSK DB6 -l SAPVIEW.log
/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: job completed
/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: END OF LOG: 20140823014048
/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: START OF LOG: 20140823014048
/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: sccsid @(#) $Id: //bas/721_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: version R7.20/V1.6 [UNICODE]
Compiled Dec 4 2013 12:54:08
/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load -i SAPVIEW.cmd -dbcodepage 4102 -l SAPVIEW.log -stop_on_error -loadprocedure fast LOAD:DEF_CRT
(DB) INFO: connected to DB
(SQL) INFO: Searching for SQL file SQLFiles.LST
(SQL) INFO: SQLFiles.LST not found
(SQL) INFO: Searching for SQL file /backup/NW7.3_EHP1/ABAP_Inst_EXP/51043228/DATA_UNITS/EXP3/DB/SQLFiles.LST
(SQL) INFO: /backup/NW7.3_EHP1/ABAP_Inst_EXP/51043228/DATA_UNITS/EXP3/DB/SQLFiles.LST not found
(SQL) INFO: Searching for SQL file .SQL
(SQL) INFO: .SQL not found
(SQL) INFO: Searching for SQL file /backup/NW7.3_EHP1/ABAP_Inst_EXP/51043228/DATA_UNITS/EXP3/DB/DB6/.SQL
(SQL) INFO: /backup/NW7.3_EHP1/ABAP_Inst_EXP/51043228/DATA_UNITS/EXP3/DB/DB6/.SQL not found
(DB) INFO: /BI0/MHIER_VERS created #20140823014054
(DB) INFO: /BI0/RALEAFNODCH created #20140823014054
(DB) INFO: /BI0/RALEAFNODSP created #20140823014054
(DB) INFO: /BI0/RBUCKET created #20140823014054
(DB) INFO: /BI0/RCALMONTH created #20140823014054
(DB) INFO: /BI0/RCALMONTH2 created #20140823014054
(DB) INFO: /BI0/RCALQUART1 created #20140823014054
(DB) INFO: /BI0/RCALQUARTER created #20140823014054
(DB) INFO: /BI0/RCALWEEK created #20140823014054
(DB) INFO: /BI0/RCALYEAR created #20140823014054
(DB) INFO: /BI0/RCHNGID created #20140823014054
(DB) INFO: /BI0/RCURRENCY created #20140823014054
(DB) INFO: /BI0/RDATE created #20140823014054
(DB) INFO: /BI0/RFISCPER created #20140823014054
(DB) INFO: /BI0/RFISCPER3 created #20140823014054
(DB) INFO: /BI0/RFISCVARNT created #20140823014054
(DB) INFO: /BI0/RFISCYEAR created #20140823014054
(DB) INFO: /BI0/RHALFYEAR1 created #20140823014054
(DB) INFO: /BI0/RHIENM created #20140823014054
(DB) INFO: /BI0/RHIER_HIEID created #20140823014054
(DB) INFO: /BI0/RHIER_NODE created #20140823014054
(DB) INFO: /BI0/RHIER_VERS created #20140823014054
(DB) INFO: /BI0/RINFOPROV created #20140823014054
(DB) INFO: /BI0/RIOBJNM created #20140823014054
(DB) INFO: /BI0/RLANGU created #20140823014054
(DB) INFO: /BI0/RLOGSYS created #20140823014054
(DB) INFO: /BI0/RNODEPOSIT created #20140823014054
(DB) INFO: /BI0/RNORESTNODE created #20140823014054
(DB) INFO: /BI0/RRATE_TYPE created #20140823014054
(DB) INFO: /BI0/RRECORDMODE created #20140823014054
(DB) INFO: /BI0/RRECORDTP created #20140823014054
(DB) INFO: /BI0/RREQUID created #20140823014054
(DB) INFO: /BI0/RSIGNCH created #20140823014054
(DB) INFO: /BI0/RSOURSYSTEM created #20140823014054
(DB) INFO: /BI0/RTIME created #20140823014054
(DB) INFO: /BI0/RTXTLG created #20140823014054
(DB) INFO: /BI0/RTXTMD created #20140823014054
(DB) INFO: /BI0/RTXTSH created #20140823014054
(DB) INFO: /BI0/RUNIT created #20140823014054
(DB) INFO: /BI0/RWEEKDAY1 created #20140823014054
(DB) INFO: /BI0/ZBUCKET created #20140823014054
(DB) INFO: /BI0/ZCALMONTH created #20140823014054
(DB) INFO: /BI0/ZCALMONTH2 created #20140823014054
(DB) INFO: /BI0/ZDATE created #20140823014054
(DB) INFO: /BI0/ZFISCPER created #20140823014055
(DB) INFO: /BI0/ZHALFYEAR1 created #20140823014055
(DB) INFO: /BI0/ZINFOPROV created #20140823014055
(DB) INFO: /BI0/ZIOBJNM created #20140823014055
(DB) INFO: /GC1/VXXX created #20140823014055
(DB) INFO: /OSP/V_RAUI_CHRD created #20140823014055
(DB) INFO: /OSP/V_RAUI_CMVD created #20140823014055
(DB) INFO: /OSP/V_RAUI_CPVD created #20140823014055
(DB) INFO: /OSP/V_RAUI_CSED created #20140823014055
(DB) INFO: /OSP/V_RAUI_DCDB created #20140823014055
(DB) INFO: /OSP/V_RAUI_GRPD created #20140823014055
(DB) INFO: /OSP/V_RAUI_MTD created #20140823014055
(DB) INFO: /OSP/V_RAUI_MVDB created #20140823014055
(DB) INFO: /OSP/V_RAUI_PBDB created #20140823014055
(DB) INFO: /OSP/V_RAUI_RDDB created #20140823014055
(DB) INFO: /OSP/V_RAUI_RFCD created #20140823014055
(DB) INFO: /OSP/V_RAUI_RMTD created #20140823014055
(DB) INFO: /OSP/V_RAUI_RTDB created #20140823014055
(DB) INFO: /OSP/V_RAUI_SCD created #20140823014055
(DB) INFO: /OSP/V_RAUI_SCHD created #20140823014055
(DB) INFO: /OSP/V_RAUI_SELD created #20140823014055
(DB) INFO: /OSP/V_RAUI_TMVD created #20140823014055
(DB) INFO: /OSP/V_RAUI_TPBD created #20140823014055
(DB) INFO: /OSP/V_RAUI_TPDB created #20140823014055
(DB) INFO: /OSP/V_RAUI_TPRD created #20140823014055
(DB) INFO: /OSP/V_RAUI_TRGD created #20140823014055
(DB) INFO: /OSP/V_RAUI_VARD created #20140823014055
(DB) INFO: /SAPAPO/GEWICHT created #20140823014055
(DB) INFO: /SAPAPO/TRENDAM created #20140823014055
(DB) INFO: /SAPAPO/VWALPROF created #20140823014055
(DB) INFO: /SAPPO/FULL_HINT created #20140823014055
(DB) INFO: /SAPPO/V_PPOCMPL created #20140823014055
(DB) INFO: /SAPPO/V_PPO_UPD created #20140823014055
(DB) INFO: /SAPTRX/A_CONDF4 created #20140823014055
(DB) INFO: /SAPTRX/EE_FLDS created #20140823014055
(DB) INFO: /SAPTRX/MSG_PARA created #20140823014055
(DB) INFO: /SAPTRX/MSG_PTAB created #20140823014055
(DB) INFO: /SAPTRX/STR_FLDS created #20140823014055
(DB) INFO: /SAPTRX/VDASFEV created #20140823014055
(DB) INFO: /SAPTRX/VDASFPAR created #20140823014055
(DB) INFO: /SAPTRX/VD_AOMIL created #20140823014055
(DB) INFO: /SAPTRX/VD_AOPAC created #20140823014055
(DB) INFO: /SAPTRX/VD_AOPAE created #20140823014055
(DB) INFO: /SAPTRX/VD_AOPAI created #20140823014055
(DB) INFO: /SAPTRX/VD_AOPAR created #20140823014055
(DB) INFO: /SAPTRX/VD_AOTD1 created #20140823014055
(DB) INFO: /SAPTRX/VD_AOTD2 created #20140823014055
(DB) INFO: /SAPTRX/VD_AOTDD created #20140823014055
(DB) INFO: /SAPTRX/VD_AOTYP created #20140823014055
(DB) INFO: /SAPTRX/VD_ASPAR created #20140823014055
(DB) INFO: /SAPTRX/VD_CONDL created #20140823014055
(DB) INFO: /SAPTRX/VD_EVTD1 created #20140823014055
(DB) INFO: /SAPTRX/VD_EVTD2 created #20140823014055
(DB) INFO: /SAPTRX/VD_EVTD3 created #20140823014055
(DB) INFO: /SAPTRX/VD_EVTD4 created #20140823014055
(DB) INFO: /SAPTRX/V_AODD02 created #20140823014055
(DB) INFO: /SAPTRX/V_DD03 created #20140823014055
(DB) INFO: /SAPTRX/V_DD03X created #20140823014055
(DB) INFO: /SDF/CMO_OBJ_TR created #20140823014055
(DB) INFO: /SDF/CMO_SMDCMP created #20140823014056
(DB) INFO: /SDF/CMO_SMDDVC created #20140823014056
(DB) INFO: /SDF/CMO_UMDCMP created #20140823014056
(DB) INFO: /SDF/SMODICOMP created #20140823014056
(DB) INFO: /SDF/SMODIDEVC created #20140823014056
(DB) INFO: /SDF/UMOD_COMP created #20140823014056
(DB) INFO: AKB_TRHD_DETAIL created #20140823014056
(DB) INFO: ALTEXTHIST created #20140823014056
(DB) INFO: APPL_DEVC created #20140823014056
(DB) INFO: APPL_DIAL created #20140823014056
(DB) INFO: APPL_DOMA created #20140823014056
(DB) INFO: APPL_DTEL created #20140823014056
(DB) INFO: APPL_ENQU created #20140823014056
(DB) INFO: APPL_FUGR created #20140823014056
(DB) INFO: APPL_FUGRG created #20140823014056
(DB) INFO: APPL_FUNC created #20140823014056
(DB) INFO: APPL_INDX created #20140823014056
(DB) INFO: APPL_MCOB created #20140823014056
(DB) INFO: APPL_MENU created #20140823014056
(DB) ERROR: DDL statement failed
( CREATE VIEW "APPL_MODS" ( "NAME", "TYP", "MEMBER", "DEVCLASS" ) AS SELECT T0001."NAME", T0001."TYP", T0001."MEMBER", T0002."DEVCLASS" FROM "MODSAP" T0001, "MODSAPA" T0002 WHERE T0001."NAME" = T0002."NAME" AND T0002."MIGRATED" <> 'X' )
dsql_exec_immediate returned DS_DBOBJECTUNKNOWN
(DB) INFO: disconnected from DB
/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: job finished with 1 error(s)
/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: END OF LOG: 20140823014056
/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: START OF LOG: 20140823014312
/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: sccsid @(#) $Id: //bas/721_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: version R7.20/V1.6 [UNICODE]
Compiled Dec 4 2013 12:54:08
/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load -i SAPVIEW.cmd -dbcodepage 4102 -l SAPVIEW.log -stop_on_error -loadprocedure fast LOAD:DEF_CRT
(DB) INFO: connected to DB
(SQL) INFO: Searching for SQL file SQLFiles.LST
(SQL) INFO: SQLFiles.LST not found
(SQL) INFO: Searching for SQL file /backup/NW7.3_EHP1/ABAP_Inst_EXP/51043228/DATA_UNITS/EXP3/DB/SQLFiles.LST
(SQL) INFO: /backup/NW7.3_EHP1/ABAP_Inst_EXP/51043228/DATA_UNITS/EXP3/DB/SQLFiles.LST not found
(SQL) INFO: Searching for SQL file .SQL
(SQL) INFO: .SQL not found
(SQL) INFO: Searching for SQL file /backup/NW7.3_EHP1/ABAP_Inst_EXP/51043228/DATA_UNITS/EXP3/DB/DB6/.SQL
(SQL) INFO: /backup/NW7.3_EHP1/ABAP_Inst_EXP/51043228/DATA_UNITS/EXP3/DB/DB6/.SQL not found
(DB) ERROR: DDL statement failed
( DROP VIEW "APPL_MODS" )
dsql_exec_immediate returned DS_DBOBJECTUNKNOWN
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
( CREATE VIEW "APPL_MODS" ( "NAME", "TYP", "MEMBER", "DEVCLASS" ) AS SELECT T0001."NAME", T0001."TYP", T0001."MEMBER", T0002."DEVCLASS" FROM "MODSAP" T0001, "MODSAPA" T0002 WHERE T0001."NAME" = T0002."NAME" AND T0002."MIGRATED" <> 'X' )
dsql_exec_immediate returned DS_DBOBJECTUNKNOWN
(DB) INFO: disconnected from DB
/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: job finished with 1 error(s)
/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: END OF LOG: 20140823014318
/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: START OF LOG: 20140823015246
/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: sccsid @(#) $Id: //bas/721_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: version R7.20/V1.6 [UNICODE]
Compiled Dec 4 2013 12:54:08
/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load -i SAPVIEW.cmd -dbcodepage 4102 -l SAPVIEW.log -stop_on_error -loadprocedure fast LOAD:DEF_CRT
(DB) INFO: connected to DB
(SQL) INFO: Searching for SQL file SQLFiles.LST
(SQL) INFO: SQLFiles.LST not found
(SQL) INFO: Searching for SQL file /backup/NW7.3_EHP1/ABAP_Inst_EXP/51043228/DATA_UNITS/EXP3/DB/SQLFiles.LST
(SQL) INFO: /backup/NW7.3_EHP1/ABAP_Inst_EXP/51043228/DATA_UNITS/EXP3/DB/SQLFiles.LST not found
(SQL) INFO: Searching for SQL file .SQL
(SQL) INFO: .SQL not found
(SQL) INFO: Searching for SQL file /backup/NW7.3_EHP1/ABAP_Inst_EXP/51043228/DATA_UNITS/EXP3/DB/DB6/.SQL
(SQL) INFO: /backup/NW7.3_EHP1/ABAP_Inst_EXP/51043228/DATA_UNITS/EXP3/DB/DB6/.SQL not found
(DB) ERROR: DDL statement failed
( DROP VIEW "APPL_MODS" )
dsql_exec_immediate returned DS_DBOBJECTUNKNOWN
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
( CREATE VIEW "APPL_MODS" ( "NAME", "TYP", "MEMBER", "DEVCLASS" ) AS SELECT T0001."NAME", T0001."TYP", T0001."MEMBER", T0002."DEVCLASS" FROM "MODSAP" T0001, "MODSAPA" T0002 WHERE T0001."NAME" = T0002."NAME" AND T0002."MIGRATED" <> 'X' )
dsql_exec_immediate returned DS_DBOBJECTUNKNOWN
(DB) INFO: disconnected from DB
/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: job finished with 1 error(s)
/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: END OF LOG: 20140823015250
/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: START OF LOG: 20140825011924
/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: sccsid @(#) $Id: //bas/721_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: version R7.20/V1.6 [UNICODE]
Compiled Dec 4 2013 12:54:08
/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load -i SAPVIEW.cmd -dbcodepage 4102 -l SAPVIEW.log -stop_on_error -loadprocedure fast LOAD:DEF_CRT
(DB) INFO: connected to DB
(SQL) INFO: Searching for SQL file SQLFiles.LST
(SQL) INFO: SQLFiles.LST not found
(SQL) INFO: Searching for SQL file /backup/NW7.3_EHP1/ABAP_Inst_EXP/51043228/DATA_UNITS/EXP3/DB/SQLFiles.LST
(SQL) INFO: /backup/NW7.3_EHP1/ABAP_Inst_EXP/51043228/DATA_UNITS/EXP3/DB/SQLFiles.LST not found
(SQL) INFO: Searching for SQL file .SQL
(SQL) INFO: .SQL not found
(SQL) INFO: Searching for SQL file /backup/NW7.3_EHP1/ABAP_Inst_EXP/51043228/DATA_UNITS/EXP3/DB/DB6/.SQL
(SQL) INFO: /backup/NW7.3_EHP1/ABAP_Inst_EXP/51043228/DATA_UNITS/EXP3/DB/DB6/.SQL not found
(DB) ERROR: DDL statement failed
( DROP VIEW "APPL_MODS" )
dsql_exec_immediate returned DS_DBOBJECTUNKNOWN
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
( CREATE VIEW "APPL_MODS" ( "NAME", "TYP", "MEMBER", "DEVCLASS" ) AS SELECT T0001."NAME", T0001."TYP", T0001."MEMBER", T0002."DEVCLASS" FROM "MODSAP" T0001, "MODSAPA" T0002 WHERE T0001."NAME" = T0002."NAME" AND T0002."MIGRATED" <> 'X' )
dsql_exec_immediate returned DS_DBOBJECTUNKNOWN
(DB) INFO: disconnected from DB
/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: job finished with 1 error(s)
/usr/sap/PID/SYS/exe/uc/rs6000_64/R3load: END OF LOG: 20140825011937
Please look into this..
Regards,
Ayan -
DDL statement/s in stored procedures (FUNCTION)
Hello all,
I was trying to create a small function that tests keywords on the basis of successful/failed table creation. If a table can be created with a keyword as identifier, it is a non-reserved keyword, if table creation fails, it is a reserved keyword:
CREATE OR REPLACE FUNCTION createTableForKeyword (keyword VARCHAR) RETURN BOOLEAN IS
BEGIN
CREATE TABLE keyword (x NUMBER);
-- if no exception occurred, table creation succeeded
DROP TABLE keyword; drop it
RETURN FALSE; -- FALSE means non-reserved
EXCEPTION
WHEN OTHERS THEN
-- if exception occurred, table creation failed
RETURN TRUE; -- TRUE means reserved
END createTableForKeyword;
This would have been my first PL/SQL program, but I get the following error:
PLS-00103: Found symbol "CREATE" when expecting one of:
begin case declare exit ................
.............. merge pipe
I had to translate the error message from German, but it should suffice. Obviously DDL statements in functions are not allowed. How do I solve my problem then, given a table that has one column containing the keyword?:
CREATE TABLE Keywords (keyword VARCHAR(30));
I was looking too call this function from a loop, but how would I do this without a function? How do I capture table creation fails without exceptions in functions?
TIA
KarstenTo run DDL inside stored procedure you must use Dynamic SQL. Use EXECUTE IMMEDIATE
To see if a word is a reserved word just query V$RESERVED_WORDS
Thanks,
Karthick. -
How to know which user has executed which ddl statement
Hi All,
Last week i faced some problem, like some one has truncated the table , so luckily i have the schema backup so i restored it till the last backup taken.
but i want to know who has executed this ddl statement.
i know there are some utilities are avaible with oracle, so please describe me the easiest and quickest way to get this.
Regards
AsifIn order of descending simplicity
- Use the principle of least privilege to restrict the privileges users have in the database to ensure that they cannot do things like truncating a table
- Enable auditing of potentially problematic statements. This has to be done before the damage is done, though
- Create a DDL trigger that logs when users issue DDL. This also must be done before the damage is done.
- Use LogMiner to go through the archived log files that were generated at the time the table was truncated. This assumes that the database is in ARCHIVELOG mode and that you have the archived logs from last week. Using LogMiner to track down the culprit is also likely to be relatively time-intensive
Justin -
Errors when executing DDL statements against MaxDB
Hi guys,
We are experiencing problems with DDL execution against MaxDB. I have installed version 7.8.00.17 on my 32-bit Windows XP XP3 machine. I got the following errors:
1. MaxDB complained that the "VARCHAR(8008)" data type has invalid length.
2. When fixing this, I got the problem, that a unique constraint has too long name.
3. After shortening this name, now I get the following:
u2190[4;35;1mSQL (0.0ms)u2190[0m u2190[0mActiveRecord::JDBCError: SAP DBTech JDBC: [-4006] (at 25): Unknown domain name:PRIMARY_KEY: CREATE TABLE photos (id primary_key, title varchar(8008), created_at timestamp, updated_at timestamp) u2190[0m
rake aborted!
All these DDL statements, are generated as part of a rake task execution (we are testing a simple Rails application, that uses persistence), and they execute fine on MySQL for instance. But on MaxDB it seems that there are more severe limitations about name lengths, data types, etc.
Could you please advice about this problem ?
Thanks and Kindest Regards,
Krum.Hmm... what's wrong with the internet on your side, that you don't have access to the MaxDB documentation?
ad 1. You are using a UNICODE varchar, aren't you? check [here|http://maxdb.sap.com/doc/7_7/45/33337d9faf2b34e10000000a1553f7/frameset.htm] why it fails.
ad 2. Unique constraints don't get names in MaxDB [see here|http://maxdb.sap.com/doc/7_7/45/50fa4272c31796e10000000a1553f6/frameset.htm]
ad 3. You're simply using the wrong DDL format. "PRIMARY_KEY" is not even a MaxDB keyword.
I'm pretty sure you'll find the correct syntax for primary key definition yourself, by simply browsing the documentation, so I leave this to you now.
regards,
Lars -
Why there is implicit commit before and after executing DDL Statements
Hi Guys,
Please let me know why there is implicit commit before and after executing DDL Statements ?
Regards,
sushmitaHelyos wrote:
This is because Oracle has design it like this.Come on Helyos, that's a bit of a weak answer. :)
The reason is that it makes no sense to update the structure of the database whilst there is outstanding data updates that have not been committed.
Imagine having a column that is VARCHAR2(50) that currently only has data that is up to 20 characters in size.
Someone (person A) decides that it would make sense to alter the table and reduce the size of the column to varchar2(20) instead.
Before they do that, someone else (person B) has inserted data that is 30 characters in size, but not yet committed it.
As far as person B is concerned that insert statement has been successful as they received no error, and they are continuing on with their process until they reach a suitable point to commit.
Person A then attempts to alter the database to make it varchar2(20).
If the database allowed that to happen then the column would be varchar2(20) and the uncommitted data would no longer fit, even though the insert was successful. When is Person B going to find out about this? It would be wrong to tell them when they try and commit, because all their transactions were successful, so why should a commit fail.
In this case, because it's two different people, then the database will recognise there is uncommitted transactions on that table and not let person B alter it.
If it was just one person doing both things in the same session, then the data would be automatically committed, the alter statement executed and the person informed that they can't alter the database because there is (now) data exceeding the size they want to set it to.
It makes perfect sense to have the database in a data consistent state before any alterations are made to it, hence why a commit is issued beforehand.
Here's something I wrote the other day on the subject...
DDL's issue a commit before carrying out the actual action
As long as the DDL is syntactically ok (i.e. the parser is happy with it) then the commit is issued, even if the actual DDL cannot be executed for another reason.
Example...
We have a table with some data in it...
SQL> create table xtest as select rownum rn from dual;
Table created.
SQL> select * from xtest;
RN
1We then delete the data but don't commit (demonstrated by the fact we can roll it back)
SQL> delete from xtest;
1 row deleted.
SQL> select * from xtest;
no rows selected
SQL> rollback;
Rollback complete.
SQL> select * from xtest;
RN
1
SQL> delete from xtest;
1 row deleted.
SQL> select * from xtest;
no rows selectedSo now our data is deleted, but not committed, what if we issue a DDL that is syntactically incorrect...
SQL> alter tab xtest blah;
alter tab xtest blah
ERROR at line 1:
ORA-00940: invalid ALTER command
SQL> rollback;
Rollback complete.
SQL> select * from xtest;
RN
1... the data can still be rolled back. This is because the parser was not happy with the syntax of the DDL statement.
So let's delete the data again, without committing it, and issue a DDL that is syntactically correct, but cannot execute for another reason (i.e. the database object it refers to doesn't exist)...
SQL> delete from xtest;
1 row deleted.
SQL> select * from xtest;
no rows selected
SQL> truncate table bob;
truncate table bob
ERROR at line 1:
ORA-00942: table or view does not exist
SQL> rollback;
Rollback complete.
SQL> select * from xtest;
no rows selectedSo, there we have it. Just because the statement was syntactically correct, the deletion of the data was committed, even though the DDL couldn't be performed.
This makes sense really, because if we are planning on altering the definition of the database where the data is stored, it can only really take place if the database is in a state where the data is where it should be rather than being in limbo. For example, imagine the confusion if you updated some data on a column and then altered that columns datatype to be a different size e.g. reducing a varchar2 column from 50 character down to 20 characters. If you had data that you'd just updated to larger than 20 characters whereas previously there wasn't, then the alter table command would not know about it, would alter the column size and then the data wouldn't be valid to fit whereas the update statement at the time didn't fail.
Example...
We have a table that only allows 20 characters in a column. If we try and insert more into that column we get an error for our insert statement as expected...
SQL> create table xtest (x varchar2(20));
Table created.
SQL> insert into xtest values ('012345678901234567890123456789');
insert into xtest values ('012345678901234567890123456789')
ERROR at line 1:
ORA-12899: value too large for column "SCOTT"."XTEST"."X" (actual: 30, maximum: 20)Now if our table allowed more characters our insert statement is successful. As far as our "application" goes we believe, nay, we have been told by the database, we have successfully inserted our data...
SQL> alter table xtest modify (x varchar2(50));
Table altered.
SQL> insert into xtest values ('012345678901234567890123456789');
1 row created.Now if we tried to alter our database column back to 20 characters and it didn't automatically commit the data beforehand then it would be happy to alter the column, but then when the data was committed it wouldn't fit. However the database has already told us that the data was inserted, so it can't go back on that now.
Instead we can see that the data is committed first because the alter command returns an error telling us that the data in the table is too big, and also we cannot rollback the insert after the attempted alter statement...
SQL> alter table xtest modify (x varchar2(20));
alter table xtest modify (x varchar2(20))
ERROR at line 1:
ORA-01441: cannot decrease column length because some value is too big
SQL> rollback;
Rollback complete.
SQL> select * from xtest;
X
012345678901234567890123456789
SQL>Obviously, because a commit statement is for the existing session, if we had tried to alter the table column from another session we would have got
SQL> alter table xtest modify (x varchar2(20));
alter table xtest modify (x varchar2(20))
ERROR at line 1:
ORA-00054: resource busy and acquire with NOWAIT specified
SQL>... which is basically saying that we can't alter the table because someone else is using it and they haven't committed their data yet.
Once the other session has committed the data we get the expected error...
ORA-01441: cannot decrease column length because some value is too bigHope that explains it -
DDL statements and dynamic sql in stored procedure
I created a stored procedure to create and drop tables, using dynamic sql.
When I try to do the inserts using dynamic sql, i.e
v_string := 'INSERT statement';
EXECUTE IMMEDIATE v_string;
I get the following error message:
ERROR at line 1:
ORA-00942: table or view does not exist
ORA-06512: at line 63
Line 63 happens to be the line that the EXECUTE IMMEDIATE v_string; statement is in.
I am able to describe the table that the inserts are being made into, so I know that the table exists.
Any idea why I'm getting this error message would be appreciated.Yes I do and I have been able to create other tables using dynamic sql.
The table that I am having problems with SELECTs data from another table to get its column values; within the SELECT statement, the CAST function is used:
ie. CAST(CASE SUBSTR(CAST(E_MOD AS VARCHAR(7)),2,3)
WHEN 'AAA' THEN 'A55'
ELSE ............
I get the following error message:
ERROR at line 18: (this line starts the CAST statement)
ORA-06550: line 18, column 13:
PLS-00103: Encountered the symbol "AAA" when expecting one of the following:
. ( * @ % & = - + ; < / > at in is mod not rem return
returning <an exponent (**)> <> or != or ~= >= <= <> and or
like between into using || bulk
When I remove the quotes or add another single quote, the same error cascades to 'A55'.
After doing the same for the next error, I get the error message below:
ERROR at line 1: (this line has the EXECUTE IMMEDIATE statement)
ORA-00936: missing expression
ORA-06512: at line 6
Any idea what the problem could be?
Also is there another way to have DDL statements as stored procedures other than using dynamic sql or the DBMS_SQL package? -
Difference B/w all DDL statements in Oracle 8i and 9i
Where can i get the difference between all the DDL statements between oracle 8i and 9i.If anyone has this pls ..post it..
What is your national character set? What is NLS_LENGTH_SEMANTICS set to?
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC -
Executing multiple DDL statements with OracleCommand
hi..
im having trouble executing multiple ddl statements with the the oracle command object. i have tried to enclose them within Begin.. End; block but with no use.
this problem seems to occur only with DDL statements,.. as my DML like update, delete and Inserts seem to work fine when enclosed within the PL /SQL block.
single DDL statements also seem to work fine. so im guessing this has nothing to do with priviledges. any ideas?
my code as follows
OracleCommand command = new OracleCommand();
command.CommandType = CommandType.Text;
command.CommandText = string.Format(@"{0}",script);
conn.Open();
command.Connection = conn;
command.ExecuteNonQuery();
the script is read from a file, and looks like this. (note : i have removed any line breaks or any other characters)
BEGIN ALTER TABLE SYSTEMUSER DISABLE CONSTRAINT FK_USER_CLIENT; ALTER TRIGGER SET_SUBSCRIPTION_SUB_I DISABLE; END;
this is the error i get.
Oracle.DataAccess.Client.OracleException: ORA-06550: line 1, column 7:
PLS-00103: Encountered the symbol "ALTER" when expecting one of the following:
begin case declare exit for goto if loop mod null pragma
raise return select update while with <an identifier>
<a double-quoted delimited-identifier> <a bind variable> <<
close current delete fetch lock insert open rollback
savepoint set sql execute commit forall merge pipe.If I'm not mistaken, we're not allowed to issue DDL inside anonymoue block (or stored procedure) since DDL has implicit commit in it. But you still can execute DDL using EXECUTE IMMEDIATE or using DBMS_SQL package. Try changing your CommandText like this,
BEGIN
EXECUTE IMMEDIATE 'ALTER TABLE SYSTEMUSER DISABLE CONSTRAINT FK_USER_CLIENT';
EXECUTE IMMEDIATE 'ALTER TRIGGER SET_SUBSCRIPTION_SUB_I DISABLE';
END;Hope this helps,
[Nur Hidayat|http://nur-hidayat.net/] -
DDL statements in Graphic builder 6i
Hi.
Is there possibility to perform DDL statements in Graphic builder 6i? Something like FORM_DDL in Forms and SRW.DO_SQL in Reports.
I want to set role. Report has own statement SET_ROLE.
Our application use classic security model: User has granted only LOGIN privilege by default. After login application sets roles for reading, writing, deleting to DB. Same Reports do. But in Graphic builder I can't.May I can use OG library and OG.Interpret command. :o)
-
Too many failed message tracking resquests via task in Exchange 2010 SP3
Hi,
We are getting this alert every day and I don't find anything to solve it...
Some days it's Yellow (3%) and the others it's Red (5%)... But we don't have 5% of the messages failed.
Do there is a solution to this problem or even somewhere to look ?To Fix your issue, try to override monitor rule of KHI: Too many failed message tracking requests via task – Red (>5%) and also rule of KHI: Too many failed message tracking requests via task – Yellow (>3%)
Also you can refer below link
http://social.technet.microsoft.com/Forums/en-US/089b0c7c-77c5-47ef-9e48-7e44a8f1d2a1/khi-too-many-failed-message-tracking-requests-via-task-in-exchange-2010-sp1-management-pack?forum=operationsmanagermgmtpacks
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Maybe you are looking for
-
Problem with iTunes (and all of iLife!!!) finding information on machine
I just bought a new G5 Black Macbook, and had the Apple Store transfer my old profile from my G4 iBook in the past week. When i picked up my macbook, everything worked fine and all the pictures, music and personal preferences were transfered, but in
-
HT4262 How can I connect 6 computers simultaneously to Airport extreme?
I have tried troubleshooting several ways and the some computers work and others don't. How can I connect 6 wireless computers to Airport Extreme?
-
RFC returns different data of SE37
I have a RFC that has a table of exit with two fileds of value (Gross Price and Tax Value). In the transaction SE37 returns the two fileds correctly. In the Web Portal (not SAP) when access the RFC with the same data, returns de same amount records,
-
Hi! :-) Does somebody knows if the created pdf slideshows, can showing the images only, without having the surrounding black border? Can Photoshop Album Starter Edition, create pdf slideshows without black borders? How? If not, what program can do th
-
Error message - iTines is not installed correctly...
When I try to use the iPod Update, it comes back with an "iPod service error". When iTunes opens, all seems okay (you can check songs, create libraries, etc.), but when you connect the iPod a message saying that "iTunes is not installed correctly, pl