This page (revision-4) was last changed on 26-Nov-2021 10:22 by jmyers

This page was created on 26-Nov-2021 10:22 by RForbes

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
4 26-Nov-2021 10:22 1 KB jmyers to previous SITE_ADMIN_EMAIL ==> SITE_ADMIN_EMAIL(System_Preference)
3 26-Nov-2021 10:22 1 KB JEscott to previous | to last
2 26-Nov-2021 10:22 1 KB RForbes to previous | to last
1 26-Nov-2021 10:22 991 bytes RForbes to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 3 changed one line
There are several [functions|FUNCTIONS] that will activate procedures in the data abse that will then execute on that server, including outputting files for interface purposes. In this case, the user on t he server that is executing the Oracle data base process must have write access to the directory indicated. Unless you change the user who is running the Oracle processes using the Contol Panel Services applet, you are limited to local (on the server) directories.
There are several [functions|FUNCTIONS] that will activate procedures in the data base that will then execute on that server, including outputting files for interface purposes. In this case, the user on t he server that is executing the Oracle data base process must have write access to the directory indicated. Unless you change the user who is running the Oracle processes using the Contol Panel Services applet, you are limited to local (on the server) directories.
At line 6 added 4 lines
The "owner" of the objects in the data base, also known as the schema owner, is the reserved data base user P2K. many operations, including the application of scripts to create [stored procedures|STORED PROCEDURE], [tables and views|TABLES and VIEWS] and other objects required for the proper functinoing of this application.
Oracle provides some additional structures that allow a user to view the data base schema. These [internal tables|ORACLE INTERNAL TABLES] also allow users with the correct permissions to view internal structures, such as locks and blocked sessions, and other session information.