Message-Id: <10661.120328@fatcity.com> From: "Eric D. Pierce" Date: Thu, 26 Oct 2000 12:07:50 -0700 Subject: Re: Is it possible to import a package alone? re: editing DD content from imp The DD data is not in the imp LOG file, it goes into an imp INDEXFILE. SHOW=y ROWS=n LOG=imp1.log *-> INDEXFILE=ifile.txt RECORDLENGTH=10000 TABLES=(TEMP_26_OCTOBER_2000) 1) (fyi) after testing (Oracle7.3/Netware), i found that the RECORDLENGTH parameter doesn't affect line length of the INDEXFILE (output) file. The INDEXFILE appears to be fixed width, around 75 fixed width characters, but at least it *does* word wrap. :) 2) the use of editor macro functions (search/replace) will make the editing process somewhat more efficient than "manual" editing. Of course with a huge set of DD objects, it is still going to be an ugly slog, just a littl easier using edit macros. exaple "INDEXFILE" output: -----begin (ifile.txt)----- REM CREATE TABLE "STUDENT"."TEMP_26_OCTOBER_2000" ("ST_TERM" CHAR(5), REM "STU_ID" CHAR(9), "STU_NAME" CHAR(32), "STU_PRV_NM" CHAR(32), REM "ST_CURR_AHRS_GROSS_UNITS" CHAR(6), "ST_ENR_HRS_NET_UNITS" CHAR(6), REM "ST_CLS_LVL_CLASS_LEVEL" CHAR(3), "ST_PRT_FL_11_PRIORITY_DSAB" REM CHAR(1), "ST_ENT_ACTN_PRIMARY_CRRNT_PROG" CHAR(2), "ADR_STREET_1" REM CHAR(32), "ADR_CITY" CHAR(20), "ADR_STATE" CHAR(2), "ADR_ZIP" REM CHAR(9), "ADR_CNTRY" CHAR(2), "STU_ETH_CODE" CHAR(1), "STU_SEX" REM CHAR(1), "STU_BIRTH_DT" CHAR(8), "ST_TCAL_OVRD_TMP_WITHDRWL_DATE" REM CHAR(8), "ST_CURR_GPA_PER_SEMESTER" CHAR(7), "ALL_GPA" CHAR(7), REM "ST_MAJR_1_MAJOR" CHAR(4), "ST_CONC_1_MAJOR_CONCENTRATION" CHAR(4), REM "ST_AC_UNIT_CONTINUING_ED" CHAR(1), "ST_DISENR_DT_DISENROLLMENTDATE" REM CHAR(8), "ST_AC_ACTN_ACADEMIC_ACTION" CHAR(2), "FULL_PART" CHAR(1)) REM PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 STORAGE(INITIAL 503808 REM NEXT 253952 MINEXTENTS 1 MAXEXTENTS 299 PCTINCREASE 0 FREELISTS 1 REM FREELIST GROUPS 1) TABLESPACE "USERS" ; -----end----- example "LOG" file: -----begin (imp1.log)----- Connected to: Oracle7 Server Release 7.3.2.3.0 - Production Release With the distributed, replication and parallel query options PL/SQL Release 2.3.2.3.0 - Production Export file created by EXPORT:V07.00.16 Import terminated successfully without warnings. -----end----- regards, ep ... > > >>> carmichr@hotmail.com 10/25/00 10:20PM >>> > >Import from an export or import from a backup? > > > >If you have an export file of a full database export taken before you > >changed the package, you can get it back, but it's not really an import, > >because just the SQL statements to recreate the database are in the export > >file. So you could do an import with rows=n show=y log= and then > >edit the log file to get the script and then run it to recreate the > >package.