The OUTLN user in the database contains the repository of your stored outlines. To move the outline from one database to another, simply export the OL$ and OL$HINTS tables and then import them to another database.
exp userid=outln/outln file=outln.dmp tables=(ol$,ol$hints)
Transfer the dump file to the other database server and import the contents:
imp userid=outln/outln file=outln.dmp full=y ignore=y
This process will transfer all stored outlines from one database to another. The entire contents of the dump file (FULL=Y) were imported. The IGNORE=Y parameter is used since the OL$ and OL$HINTS tables already exist in the destination database.
If you do not want to transfer all outlines, use the WHERE parameter of the export utility to export the stored outlines for a specific category. To export the stored outlines of the EMPLOYEE_APPLICATION category only, invoke the export utility as follows:
exp userid=outln/outln file=outln.dmp tables=(ol$,ol$hints)
query="where category='employee_application'"
One dump file can be created for each stored outline category. This is a very nice way of backing up outlines.
Application developers should get used to the idea of creating stored outlines to promote plan stability. This way, your application will run as you intended it to run. Part of the application installation procedure would be to add the stored outline to the database. The application would automatically set the USE_STORED_OUTLINES parameter (described below) to begin using that outline.
0 comments:
Post a Comment