Dbms_metadata.get_ddl output format is not runable.

Hi,
I am using dbms_metadata.get_ddl to extract the objects. But the output returned is not runable.
In output lines are broken so it makes unable to run that code.
Ex. If I run this for all the synonyms like this.
set pagesize 0
set long 90000
set feedback off
set echo off
spool /tmp/FixSyn.out
select
DBMS_METADATA.GET_DDL('SYNONYM',u.object_name,'ADMINSRV_D1')
from
dba_objects u
where
object_type = 'SYNONYM' and owner= 'ADMINSRV_D1';
spool off;
Output from this is coming like this.
CREATE OR REPLACE SYNONYM "ADMINSRV_D1"."ASSTATEAPPORVALTYPE222" FOR "ADMINSRV
_D1"."ASSTATEAPPORVALTYPE";
CREATE OR REPLACE SYNONYM "ABC"."ASSTATEAPPORVALTYPE3" FOR "ADMINSRV_D
1"."ASSTATEAPPORVALTYPE";
This is broken in multiple lines so not possible to run this.
Please provide any solution to fix this output.
Thanks a lot,
Amit.

How about using word_wrapped
set pagesize 0
set long 90000
set lines 131
column txt format a121 word_wrapped
set feedback off
set echo off
spool /tmp/FixSyn.out
select
DBMS_METADATA.GET_DDL('SYNONYM',u.object_name,'ADMINSRV_D1') txt
from
dba_objects u
where
object_type = 'SYNONYM' and owner= 'ADMINSRV_D1';
spool off;
For help on Column and default attributes.
SQL> help column
You can also check asktom replies.
http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:30802454515375
Regards,
Sabdar Syed.

Similar Messages

DBMS_METADATA.GET_DDL - output trucating

Hi,
I am generating Database Package Scripts using the following.
=====================================================
set pagesize 0
set long 90000
set feedback off;
column DDL format a80 WORD_WRAPPED
spool FMONTUSER_PACKAGE.sql
select dbms_metadata.get_ddl(object_type,object_name,owner) DDL from dba_objects
where owner='FMONTUSER' and
object_type in('PACKAGE');
spool off;
============================================
This is the last PROCEDURE of Last PAKCGE in FMONTUSER_PACKAGE.sql
=============================================
PROCEDURE insert_loan_year_end_data(argloan_id IN LOAN.LOAN_ID%TYPE,
arg_temp_prio_end_row IN TEMP_PRIOR_YEAR_END%ROWTYPE)
IS
v_as_of_dt LOAN_YEAR_END_DATA.ASOFDATE%TYPE;
BEGIN
-- Insert the record into original loan table
DBMS_OUTPUT.put_line ('before insert LOAN_YEAR_END_DATA');
v_as_of_dt := arg_temp_prio_end_row.AS_OF_DATE;
INSERT INTO LOAN_YEAR_END_DATA VALUES(LOAN_YEAR_END_DATA_SEQ.NEXTVAL,argloan_id,
arg_temp_
prio_end_row.BEGINNING_PRINCIPAL_BAL,arg_temp_prio_end_row.YTD_PRINCIPAL_PAID,
=============================================
I am getting trucated some lines in this procedure.
I increased 'set long 90000' to 'set long 100000'
Still I am getting truncated output.
Please help me to solve this.
regards,
Mathew

Hi,
This script I am using.
=======================================
set pagesize 0
--set long 90000
set long 2000000000
set feedback off;
column DDL format a80 WORD_WRAPPED
EXECUTE dbms_metadata.set_transform_param(DBMS_METADATA.SESSION_TRANSFORM,'SQLTERMINATOR',true);
EXECUTE dbms_metadata.set_transform_param(DBMS_METADATA.SESSION_TRANSFORM,'PRETTY',true);
EXECUTE dbms_metadata.set_transform_param(DBMS_METADATA.SESSION_TRANSFORM,'CONSTRAINTS',true);
EXECUTE dbms_metadata.set_transform_param(DBMS_METADATA.SESSION_TRANSFORM,'REF_CONSTRAINTS',false);
EXECUTE dbms_metadata.set_transform_param( DBMS_METADATA.SESSION_TRANSFORM, 'CONSTRAINTS_AS_ALTER', false);
EXECUTE dbms_metadata.set_transform_param( DBMS_METADATA.SESSION_TRANSFORM, 'STORAGE', false );
EXECUTE dbms_metadata.set_transform_param( DBMS_METADATA.SESSION_TRANSFORM, 'SEGMENT_ATTRIBUTES', false );
EXECUTE dbms_metadata.set_transform_param( DBMS_METADATA.SESSION_TRANSFORM, 'TABLESPACE', false );
spool FMONTUSER_PACKAGE.sql
REM -------------------------------------------------------------------------------------------------------
REM FMONTUSER_PACKAGE.sql
REM PACKAGE.sql
select dbms_metadata.get_ddl(object_type,object_name,owner) DDL from dba_objects
where owner='FMONTUSER' and
object_type in('PACKAGE');
spool off;
regards
Mathew

Setting DBMS_METADATA.GET_DDL Output for Materialized Views

Hi all.
My Oracle version is 10g.
I'm extracting the DDL of all the objects from database using the DBMS_METADATA package. I'm using SET_TRANSFORM_PARAM to configure the output because I need a simple sql code, without information about tablespaces, storage and segment attributes. Everything works fine except when I'm working with mviews object types. I can't remove the information about tablespace, storage or segment attributes for materialized views.
I would like to know if there's a related issue about it. Or there's something missing in my code?
I tried to specify the object type as another parameter on DBMS_METADATA.SET_TRANSFORM_PARAM but don't work too.
The only transform parameter that works fine with Materialized Views is the SQLTERMINATOR.
See how I have done:
declare
vDDL clob;
begin
dbms_metadata.set_transform_param (DBMS_METADATA.SESSION_TRANSFORM, 'STORAGE', FALSE);
dbms_metadata.set_transform_param (DBMS_METADATA.SESSION_TRANSFORM, 'TABLESPACE', FALSE);
dbms_metadata.set_transform_param (DBMS_METADATA.SESSION_TRANSFORM, 'SEGMENT_ATTRIBUTES', FALSE);
dbms_metadata.set_transform_param (DBMS_METADATA.SESSION_TRANSFORM, 'SQLTERMINATOR',TRUE);
select dbms_metadata.get_ddl ('MATERIALIZED_VIEW', 'MV_STO020', 'HIS117_CHECK') into vDDL FROM DUAL;
dbms_output.put_line (vDDL);
end;
and how the output is:
CREATE MATERIALIZED VIEW "HIS117_CHECK"."MV_STO020"
ORGANIZATION HEAP PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOGGING
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "TS_HIS117"
BUILD IMMEDIATE
USING INDEX
REFRESH FORCE ON DEMAND
WITH PRIMARY KEY USING DEFAULT LOCAL ROLLBACK SEGMENT
DISABLE QUERY REWRITE
AS SELECT
STO020_MOVEMENT_LOG_ID STO020_MOVEMENT_LOG_ID
, STO020_QUANTITY STO020_QUANTITY
, STO020_DATE STO020_DATE
, STO020_BEFORE_BALANCE STO020_BEFORE_BALANCE
, STO011_PRODUCT_MOVEMENT_ID STO011_PRODUCT_MOVEMENT_ID
, ADM082_PRODUCT_ID ADM082_PRODUCT_ID
, ADM089_PRODUCT_PRESENTATION_ID ADM089_PRODUCT_PRESENTATION_ID
, STO010_MOVEMENT_TYPE_ID STO010_MOVEMENT_TYPE_ID
, STO001_STOCK_ID STO001_STOCK_ID
, STO001_TARGET_STOCK_ID STO001_TARGET_STOCK_ID
, STO003_PRODUCT_LOT_ID STO003_PRODUCT_LOT_ID
, SYS010_USER_ID SYS010_USER_ID
, EIR001_MPI EIR001_MPI
, ADM056_MEDICAL_ATTENTION_ID ADM056_MEDICAL_ATTENTION_ID
, ADM094_USE_UNIT_ID ADM094_USE_UNIT_ID
FROM
STO020_MOVEMENT_LOG;
Thank you in advanced!
Edited by: lucporto on 28/08/2012 07:26

Right. I found this way but I consider this just a quick fix, because I think there should be a better way to do this.
create table t_clob (c_long);
declare
p clob;
begin
delete from t_clob;
execute immediate 'insert into t_clob (select to_lob(query) from dba_mviews where owner = :1 and mview_name = :2)'
USING 'HIS117', 'MV_STO020';
select 'CREATE MATERIALIZED VIEW MV_STO020' || chr(10) ||
'REFRESH ON DEMAND' || chr(10) || 'AS' || CHR(10) || mv.c_long
into p
from t_clob mv;
dbms_output.put_line(p);
end;
Thanks all.

Output format does not match project settings

I'm a 3d animator creating a personal demo reel. I want to create a quicktime movie.
1) create a new project, DV NTSC (720x480).
2) import source material (QT movies and TIF's) that are 720x480.
3) export using compressor set to a 720x480 format (eg DV NTSC 4:3).
4) Problem: the exported quicktime comes out at 640x480, and the contents are visibly stretched.
Why?
What should I set my project to?
What format does my source material need to be in before import?
What should I set compressor to at export?
I have tried setting the project to 640x480, but then found that I need to scale my source material to 720x480, otherwise it appears stretched in the exported movie.
Thanks!

I'd like to do two things 1) quicktime movie that I can put online, and 2) dvd.
Say I have a TIF still image. It's 720x480. I want to export that out of FCP and watch it in QuickTime Player. I guess my question is how do I make the result in QT Player look the same as it did in FCP?
I just tried setting the pixel aspect ratio to 0.9 in Photoshop, but got the same result.
Will I need to have two completely different FCP projects, one for online and one for dvd?
(yes, the exported file did look the same when I brought it back into FCP)

F110 DME Output Format

I am using DME in F110 to generate my output.
The output format is not correct.
Ideally, each segment (that was created in DMEE) should start on a new line in the output.
But, the segments appear sequentially.
For example:
FH00 Record Type, Product #, Client ID etc..BH00 Record Type Location # etc...
I want BH00 to start from a new line so it looks like this:
FH00 Record Type, Product Code, Client ID etc..
BH00 Record Type Location Code etc...
What do I do?
I believe I have to use the carriage return functionalit but dunno how.
I tried inserting empty segments in DME format tree for generating CR/LF
But that didn't work out.
Any suggestions?
Thanks for your time
Vj

Hi Ashokkumar:
I left the Fmt-spec.strct field blank, entered all the other values, but I still can't get the segments in the output to start from a new line.
For segment properties/values, under "End of Segment" I selected "Define Different Settings For This Segment" and checked on "Carriage Return"
Still doesn't work out.
Is there anything else I am missing?
Any suggestions?
Vj

DBMS_METADATA.GET_DDL- how does it format output

I call "DBMS_METADATA.GET_DDL" to get package body source code, see example call below.
Can i be always sure that it will always:
1. Return schema name before package name as for example this: "MYSCHEMA"."COLLECTSTATS". Or may it return sometimes without schema/owner-name the package name as " CREATE OR REPLACE PACKAGE BODY "COLLECTSTATS" IS"
2. Will it always be in capital letters the "owner.packagename" part?
3. wil lthere always be Double quotes surrounding package name and owner name as "MYSCHEMA"."COLLECTSTATS"?
select DBMS_METADATA.GET_DDL('PACKAGE_BODY','COLLECTSTATS','MYSCHEMA') from DUAL;
Result:
CREATE OR REPLACE PACKAGE BODY "MYSCHEMA"."COLLECTSTATS" IS
PROCEDURE save_log(p_logrec IN LiveStatsLog%ROWTYPE) IS

Can i be always sure that it will always:
1. Return schema name before package name as for example this: "MYSCHEMA"."COLLECTSTATS". Or may it return sometimes without schema/owner-name the package name as " CREATE OR REPLACE PACKAGE BODY "COLLECTSTATS" IS"This is controlable through a parameter
2. Will it always be in capital letters the "owner.packagename" part?If you have created object names with double quotes when you defined it like:
Create package "p"then no, it will keep the case as it appears in the data dixtionary. If you never use double quotes when creating objects, then ot will always be upper case.
3. wil lthere always be Double quotes surrounding package name and owner name as "MYSCHEMA"."COLLECTSTATS"?Yes, this is done so that case can be preserved if neccessary.
John

Output cut off from dbms_metadata.get_ddl

When I execute DBMS_METADATA.GET_DDL('TABLE','table_name','schema_name'), the output for some tables is cut off. When I run it from SQL Plus or Toad, it works fine. Is there a setting that I am missing.
Thanks

[email protected] wrote:
When I execute DBMS_METADATA.GET_DDL('TABLE','table_name','schema_name'), the output for some tables is cut off. When I run it from SQL Plus or Toad, it works fine. Is there a setting that I am missing.You did not tell where are you running the dbms_metadata package.
If you can set long 10000 on the client utility try this then.
Otherwise SQLPLUS is the best way to extract metadata and spool it to the file.
HTH
SS

XML Publisher report output in RTF format does not display full page

Hi,
We have one XML Publisher report, the output of report in RTF format is not getting displayed in Full Page in normal way (MS Word -->View menu --> Print layout) but we can see full page display when we do MS Word -->View menu --> Outline.
Appreciate your valuable inputs on this.
Is this a template issue or any profiles needs to be set.
Thanks
Vijay

Do you have any header and footer on your template?
If you have any header and footer then try to adjust it as of to display full page.
Thanks
Yasar

Output format in background is not same as Foreground

Dear All,
I am running a report in Background but output is not coming in desired format. Suppose output contains 35 columns ( while running the report in Foreground) but in doesn't show all the columns in background. Is there any SAP Standard settings by which we can set the output format as per our requirement while running the job in background.

Thanx Sourabh for your reply,
I have check the variant , it is correct. It's a common problem that end users are facing in my organization.
What I want that if standard output has width of 35 columns ( in foreground ), it must show all the columns in background also.

Dbms_metadata.get_ddl not working in 11g

Hi All,
I need a quick help from you. Following is not working in 11g.
dbms_metadata.get_ddl( 'MATERIALIZED_VIEW', Mview_name, owner )
It is throwing me an error saying the Materialized view does not exist, though its exist.
Please let me know, what is wrong here with 11g.

Please let me know, what is wrong here with 11g.No problem here: Can you reproduce these steps:
SQL> select * from v$version where rownum = 1
BANNER
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
1 row selected.
SQL> create materialized view mv_dummy as select * from dual
Materialized View created.
SQL> select dbms_metadata.get_ddl ('MATERIALIZED_VIEW', 'MV_DUMMY', user) ddl from dual
DDL
CREATE MATERIALIZED VIEW "MICHAEL"."MV_DUMMY" ("DUMMY")
ORGANIZATION HEAP PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOG
GING
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "USERS"
BUILD IMMEDIATE
USING INDEX
REFRESH FORCE ON DEMAND
USING DEFAULT LOCAL ROLLBACK SEGMENT
USING ENFORCED CONSTRAINTS DISABLE QUERY REWRITE
AS select * from dual
1 row selected.?

DBMS_METADATA.GET_DDL Not working

Hi All,
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
I am creating table as:
create table XX as select * from fnd;
   select   DBMS_METADATA.GET_DDL('TABLE','xx') from dualI get the below given error:
Error starting at line 1 in command:
select DBMS_METADATA.GET_DDL('TABLE','xx') from dual
Error report:
SQL Error: ORA-31603: object "xx" of type TABLE not found in schema "A395513"
ORA-06512: at "SYS.DBMS_METADATA", line 1548
ORA-06512: at "SYS.DBMS_METADATA", line 1585
ORA-06512: at "SYS.DBMS_METADATA", line 1902
ORA-06512: at "SYS.DBMS_METADATA", line 2793
ORA-06512: at "SYS.DBMS_METADATA", line 4333
ORA-06512: at line 1
31603. 00000 - "object \"%s\" of type %s not found in schema \"%s\""
*Cause:    The specified object was not found in the database.
*Action:   Correct the object specification and try the call again.

Oracle names are stored in dictionary in upper case (unless quoted name is used at create time). Use XX as table name:
SQL> create table XX as select * from emp;
Table created.
SQL> set long 1000
SQL> select   DBMS_METADATA.GET_DDL('TABLE','xx') from dual;
ERROR:
ORA-31603: object "xx" of type TABLE not found in schema "SCOTT"
ORA-06512: at "SYS.DBMS_METADATA", line 1548
ORA-06512: at "SYS.DBMS_METADATA", line 1585
ORA-06512: at "SYS.DBMS_METADATA", line 1902
ORA-06512: at "SYS.DBMS_METADATA", line 2793
ORA-06512: at "SYS.DBMS_METADATA", line 4333
ORA-06512: at line 1
no rows selected
SQL> select   DBMS_METADATA.GET_DDL('TABLE','XX') from dual;
DBMS_METADATA.GET_DDL('TABLE','XX')
CREATE TABLE "SCOTT"."XX"
   (    "EMPNO" NUMBER(4,0),
        "ENAME" VARCHAR2(10),
        "JOB" VARCHAR2(9),
        "MGR" NUMBER(4,0),
        "HIREDATE" DATE,
        "SAL" NUMBER(7,2),
        "COMM" NUMBER(7,2),
        "DEPTNO" NUMBER(2,0)
   ) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOGGING
DBMS_METADATA.GET_DDL('TABLE','XX')
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "USERS"
SQL> SY.

Dbms_metadata.get_ddl returns text of table script but not the view

Hi all
I am using a DDL trigger like
CREATE OR REPLACE TRIGGER SYS.log_ddl AFTER DDL
ON DATABASE
declare
n_text varchar2(2000);
begin
if ora_sysevent='CREATE' and ora_dict_obj_type='VIEW' then
select dbms_metadata.get_ddl
(ora_dict_obj_type ,ora_dict_obj_name,ora_dict_obj_owner)
into n_text from dual;
elsif ora_sysevent='CREATE' and ora_dict_obj_type='TABLE' then
select dbms_metadata.get_ddl
(ora_dict_obj_type ,ora_dict_obj_name,ora_dict_obj_owner) into n_text from dual
end if;
end;
on execution
the first condition produces an error if the view does not already exists
ORA-31603: object "TEST" of type VIEW not found in schema "SHAI"
but the second condition of table creation executs successfuly and return the script of the table
what can be the main theory behind this.

I think some of the bug fixes were targeted for 9.2.0.5, but I can't tell you for certain.
One of the things I really don't like about DBMS_METADATA is that it returns an error if a specified object does not exist. For example, I created a sql script that would accept a schema name as the input parameter and would generate all the ddl for the schema. If the schema did not have a particular object, for example a sequence, the call to DBMS_METADATA to generate the sequence ddl would return an error instead of returning nothing. I had error checking in the script, so this caused problems. (Oracle's response is that this is expected behaviour).
This might be what is happening with your call.
Dan

Why dbms_metadata.get_ddl can not work for db link?

db: 10.2.4
os: RH linux 5
our problem is that we can not get ddl from dbms_metadata.get_ddl for database link, however the db link does exist here as below.
SQL> select * from dba_db_links where owner='XXRPTH';
OWNER DB_LINK USERNAME HOST CREATED
XXR TO_DOPDB.XXR.COM TEST db_opdb 18-FEB-08
XXR XXRPTH_OPDBC.XXR.COM TEST db_opdb 15-JUL-08
XXR XXRPTH_BLIS.XXR.COM BLIS dbls 02-JUN-08
SQL> select dbms_metadata.get_ddl('DB_LINK','XXRPTH_OPDBC.XXR.COM','XXR') from dual;
ERROR:
ORA-31603: object "XXRPTH_OPDBC.XXR.COM" of type DB_LINK not found in schema "XXR"
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105
ORA-06512: at "SYS.DBMS_METADATA", line 2806
ORA-06512: at "SYS.DBMS_METADATA", line 4333
ORA-06512: at line 1
appreciate for any guides
thanks

I ran into this in a slightly different form, I can't remember all the rules and details, but to work around it I had to specify a fake name appendage in the db link creation in order to keep it from automatically appending the global domain.
Something like
create database link abcdef.remotealias connect to ... using 'remotealias'
rather than
create database link abcdef connect to... using 'remotealias'
At least I think it was fake, I was flopping around trying things until I got it to work, and I wound up making it the same as the tnsnames alias. I think I decided I didn't have to, but left it as the lesser of two confusions, and was miffed that the creation scripts I had been using for years suddenly had to be fixed. Yeah, it was my own damned fault, but I still think the way this works is crazy. Now hopefully someone will explain this simply so I look foolish.

APEX BIP report query output format - not able to set with a variable

I have a Named Columns (RTF) report that is working great, but I can't control the output format with a variable. I can set the "Output Format" in the Report Query Attributes, but it doesn't work when I set the report output format to "Derive from item". No matter what the item contains, I always get PDF output. I can see the variable in my session, but it doesn't control the output format. I have tried using the values "xml", "XML", "rtf", and "RTF".
Any help would be appreciated...

My guess is that an exception is being thrown for some rows. Since you've stubbed out your catch phrase to do nothing you're not going to have any visibility into what exception was thrown. You need to put some kind of logging in the catch phrase to see
what is happening.

Oracle reports output in excel format does not display the graphs

Oracle reports output in excel format does not display the graphs: "linked image cannot be displayed".
The output file in PDF format the graph is supported.

Do you have any header and footer on your template?
If you have any header and footer then try to adjust it as of to display full page.
Thanks
Yasar

Dbms_metadata.get_ddl output format is not runable.

Similar Messages

Maybe you are looking for