Splošen link:
https://docs.oracle.com/en/database/oracle/oracle-database/19/index.html
Primeri shem:
20 tips to bring more value into your Oracle Forms solutions …
Forms 12 install
https://csenthilmurugan.files.wordpress.com/2015/12/oracle_forms_12c_installation_for_windows.pdf
Hasan blog
https://hasanjawaid.blogspot.com/p/installing-oracle-12c-weblogic.html
Kaj je ADR ?
The ADR Directory
Much of what was stored in the admin directory in Oracle 10g and earlier has now been moved to the Automatic Diagnostic Repository,or ADR directory, in Oracle 11g. The ADR directory is created in $ORACLE_BASE/diagand contains a subdirectory for each different Oracle installation type on the system and may also contain some empty directories for products which are not installed. Within the database, the ADR location is defined by the diagnostic_dest initialization parameter, and the background_dump_dest, user_dump_dest and similar parameters have been deprecated.
The structure of ADR allows for the storage of items like listener logs and diagnostic files to be stored in a format which is not specific to a particular instance or even Oracle home on the system. Similarly, other aspects of Oracle like ASM have specific log locations within the ADR.
Diagnostic files for a specific database on the system are stored within the ADR under $ORACLE_BASE/diag/database_name/instance_name. In non-RAC implementations, the database and instance names are typically the same, but this format affords the flexibility needed in a RAC environment where the instance name varies from the database name.
In 11g, two versions of the alert log are maintained in the ADR directory. One, an XML file named log.xml, can be found in the ADR directory for that instance under the alert subdirectory. An XML reader or web browser should allow viewing the XML version of the log. Another text-only version of the alert log named with the traditional alert_ORACLE_SID.log is kept in the trace subdirectory and can be viewed with a standard text editor.
Managing the ADR
Along with the new ADR structure, Oracle has introduced a tool called adrci to manage the ADR. Through adrci, the amount of time can be set to retain certain information and purge information older than this time.
The adrci command is found in the $ORACLE_HOME/bin directory, so if oraenv has been run, it will be part of the path. Once launched, issue the show homes command to show ADR repositories which can be managed, then use the set homepath command to select one.
$ adrci
ADR base = “/u01/app/oracle”
adrci> show homes
ADR Homes:
diag/rdbms/test/TEST
adrci> set homepath diag/rdbms/test/TEST
With the homepath set, examine the retention period with the show control option. The retention period is indicated by the shortp_policy and longp_policy values and in 11g, is set in hours.
adrci> show control
ADR Home = /u01/app/oracle/diag/rdbms/test/TEST:
****************************************************************
ADRID SHORTP_POLICY LONGP_POLICY
——————– ——————– ————-
4124447422 720 8760
1 rows fetched
The output may wrap over several lines, but it is the second and third values that should be of interest. These values for shortp_policy and longp_policy are set in hours. Certain information like incidents and problems are retained based on the longp_policy while other information like dump files, which can be significantly larger, are deleted based on the shortp_policy.
The retention periods for these policies can be set using the set control command. To apply the current retention policy to remove diagnostic information which is older than the policy, run the purge command.
adrci> set control (shortp_policy = 128)
adrci> set control (longp_policy = 720)
adrci> show control
ADR Home = /u01/app/oracle/diag/rdbms/test/TEST:
***************************************************************
ADRID SHORTP_POLICY LONGP_POLICY
——————– ——————– ——————–
4124447422 128 720
adrci> purge
Posted from: http://www.dba-oracle.com/t_linux_oracle_adr_directory.htm