DBA_实践指南系列8_Oracle Erp R12数据维护模式Adadmin(案例)

简介: 2013-12-08 Created By BaoXinjian 一、摘要 ADADMIN是用于Oracle APPS文件系统和数据库的维护工作,是APPS DBA常用的工具。 AD Administration Main Menu   1.

2013-12-08 Created By BaoXinjian

一、摘要


ADADMIN是用于Oracle APPS文件系统和数据库的维护工作,是APPS DBA常用的工具。

AD Administration Main Menu

 

1.Generate Applications Files menu

2.Maintain Applications Files menu

3.Compile/Reload Applications Database Entities menu

4.Maintain Applications Database Entities menu

5.Change Maintenance Mode

6.Exit AD Administration

 

二、Generate Applications Files menu


1. Generate Applications Files menu

2.1. Generate message files

This task generates message binary files in the $PROD_TOP/mesg directory from oracle application object library tables.

We generally perform this task only when instructed to do so in a readme file of a patch.

2.2. Generate form files

(1). form

把$AU_TOP/forms/<LANG>/下的fmb文件生成<PROD>_TOP/forms/<LANG>下的fmx文件

(2). library

把$AU_TOP/resource/下的pll文件重新生成plx文件

(3). menu

把FNDMENU.mmb编译FNDMENU.mmx

2.3. Generate report files

根据安装语言生成report文件(.rdf)

2.4. Generate graphics files

This task generates Oracle graphics files for all installed languages.

Extension of the file name like (*.ogd),The serious of prompts and actions in this task are very similar to the prompts and actions in the Generate form files task.

2.5. Generate product JAR files

GenerateJava archive (JAR) files whenever you upgrade the Developer technology stack orwhen recommended by Oracle Support Services.

It signs JAR files (if on the Webserver) and does the following:

(1). Generates product JAR files in JAVA_TOP and copies them to APPL_TOP.

(2). Generates other Java-related files under APPL_TOP and JAVA_TOP.

(3). Recreates Java libraries (appsborg.zip and appsborg2.zip) under APPL_TOP andJAVA_TOP.

 

三、Maintain Applications Files menu


1. Maintain Applications Files主要是用于保持你的系统文件最新。比如,你需要拷贝文件从一个特定位置或者转换文件的字符集

1. Relink Applications programs

Relinks Oracle Applications executable programs with the Oracle server libraries so that they function with the Oracle database.

For each product, choose whether to link all executables or only specific ones.

Note:The default is to relink without debug information.

Use the debug option only when requested to do so by Oracle Support Services.

2.2. Create Applications environment file

2.3. Copy files to destinations

Copies files from each product area to central locations where they can be easily referenced by non-Applications programs.

This option uses revision-based copy logic to ensure that the destination file versions are the same as, or higher than, the source file versions.

The file types and their respective destinations are shown in the following table:

These files:                                               copied to (UNIX)

Java files                                                   $JAVA_TOP

HTML files                                                 $OAH_TOP

Media files                                                 $OAM_TOP

Note:When this option is used to copy reports or graphics files, the default destinationis under AU_TOP.

2.4.Convert character set

Preparesthe files in the APPL_TOP for conversion to another character set, and then performs the conversion.

When you choose this option, AD Administration presents another submenu, which contains options for scanning your files in preparation for the conversion.

The scan searches for exceptions — files that will have incomplete (lossy)conversions — so that you can fix potential problems before you actually convert the character set.

Choose one of the following scan options.

1. Scan the APPL_TOP for exceptions. Scans the APPL_TOP and creates three files in the admin\<SID>\out directory.

File                                                     Contents

admanifest_excp.lst                          Lists files that will not be converted because of lossy conversion. admanifest.lst                             Lists files thatcan be converted.         

admanifest_lossy.lst                         Lists files with lossy conversions, including line by line detail.

Review the files listed in admanifest_excp.lst. Fix files that report lossy conversion before you convert the character set. Repeat this task until there are no entries in admanifest_excp.lst. If you need to see more detail, review admanifest_lossy.lst.

2. Scan a CUSTOM directory for exceptions. Collects the same information as the firsttask,but scans custom Applications directories rather than the APPL_TOPdirectory.

3. Convert character set. Run this task only if admanifest_excp.lst has no entries. Itprompts you for the manifest file (admanifest.lst) created when you ran the scan option(s).

The utility backs up the product source files and the APPL_TOP/admin source files. It saves product files in the <PROD>_TOP directories in the format<prod>_ s_<char_set>.zip. It saves admin source files in the APPL_TOP/admin directory in the format admin_s_<char_set>.zip

2.5. Maintain snapshot information

There are two types of snapshots: APPL_TOP snapshots and global snapshots.

An APPL_TOP snapshot lists patches and versions of files in the APPL_TOP.

A global snapshot lists patches and latest versions of files in the entire Applications system (that is, across all APPL_TOPs).

Both APPL_TOP snapshots and global snapshots may be either current view snapshots or named view snapshots.

A current view snapshot is created once and updated when appropriate to maintain a consistent view. A partial view snapshot allows you to synchronize only selected files from a current view. A named view snapshot is a copy of the current view snapshot at a particular time (not necessarily the latest current view snapshot) and is not updated.

Maintain Snapshot Information menu options :

■ List snapshots (stored in the system)

■ Update current view snapshot (full or partial APPL_TOP and global)

■ Create named snapshot (select a current view snapshot to copy and name)

■ Export snapshot to file (select one to export to a text file)

■ Import snapshot from (a text) file

■ Delete named snapshot (select a snapshot for deletion)

2.6. Check for missing files

Verifies that all files needed to run Oracle Applications for the current configuration are in the current APPL_TOP.

Choose this task if you suspect there are files missing in your APPL_TOP.

 

四、Compile/Reload Applications Database Entities menu


1. Compile/Reload Applications Database Entities menu:

编译或者重新加载数据库entities,可以使用“Compile/Reload Applications Database Entities”里的菜单项。

比如你上传了一个新的菜单项,或者打了一个更改flexfield设置的patch,可以运行菜单中相关项。

 

1. Compile APPS schema

Spawns parallel workers to compile invalid database objects in the APPS schema.

Note: The need for a separate MRC schema has been removed in this release, as has the associated prompt to run Invoker Rights.

2.2. Compile menu information

Compiles menu data structures.

Choose this task after you have uploaded menu entries to the FND_MENU_ENTRIES table, or if Compile Security concurrent requests submitted from the Menus form (after changing menu entries) fail for any reason.

AD Administration asks if you want to force compilation of all menus.

If you choose the default (No), only menus with changes are compiled. If you enter Yes, all menus are compiled.

Compiling all menus is generally not advised.

2.3. Compile flexfields

Compiles flexfield data structures in Oracle Application Object Library (FND) tables.

Choose this task after you apply a patch that changes the setup of flexfields.

Patches usually indicate when you should perform this step.

Flexfields automatically compile data when you use them for the first time, so running this task is not required.

However, compiling flexfield data at a specific time (for example, when system use is low), rather than automatically at first use, can alleviate potential runtime performance issues

2.4. Reload JAR files to database

Reloads all appropriate Oracle Applications JAR files into the database. Choose this task if all Oracle Applications Java classes are removed from your database.

for example, if the database Java Virtual Machine (JVM) is reloaded because of a corrupt database.

 

五、Maintain Applications Database Entities menu


1.  Maintain Applications Database Entities menu

During normal system use, the integrity of your database can be compromised, for example through user error or after you apply a large patch.

It’s a good idea to verify the integrity of database entities as a regular maintenance procedure, or whenever the behavior of your system indicates that database entities may have been corrupted.

Some tasks on this menu report on issues, or potential issues, with database entities, and others actually remedy the issues.

Run these tasks only on the node where the core AD technology directories (the administration server) are located.

2.1. Validate APPS schema

Verifies the integrity of the APPS schema. It produces a report named <APPS schema name>.lst that lists issues and potential issues, grouped by the action required:

■ Issues you MUST fix (not specific to the APPS schema)

■ Issues you MUST fix (specific to the APPS schema)

■ Issues you may want to address (specific to the APPS schema).

The report is located in $APPL_TOP/admin/<SID>/out (UNIX), where <SID> is the value of the ORACLE_SID or TWO_TASK variable, or in %APPL_ TOP%\admin\<SID>\out (Windows),

where <SID> is the value of the LOCAL variable. Each section of the file contains instructions for resolving the issues that are listed. Most issues can be fixed by either compiling invalid database objects or recreating grants and synonyms.

2.2.Re-create grants and synonyms for APPS schema

This task recreates grants and synonyms for the Oracle Applications public schema (APPLSYSPUB), recreates grants on some packages from SYSTEM to APPS,

and spawns parallel workers to recreate grants and synonyms linking sequences and tables in the base schemas to the APPS schema.

Typically, you run this task after the Validate APPS schema task has reported issues with missing grants and synonyms.

 

3.Maintain multi-lingual tables

Run this task after you add a language. It prompts you for the number of workers, then updates all multilingual tables.

4.Check DUAL table

Some Oracle Applications products must access the DUAL table. It must exist in the SYS schema and contain exactly one row. This tasks verifies the existence of this table and the single row.

5.Maintain Multiple Reporting Currencies schema

It invokes PL/SQL packages which maintain database objects for these features. (See admntmls.pls and admntmcr.pls in $AD_TOP/admin/sql)

MRC and MLS are both implemented using "adjunct APPS schemas", meaning a complete copy of the objects in each APPS schema is replicated (and enhanced, in some cases) into an APPS_MRC and/or APPS_MLS schema. Whenever a change is made to an APPS schema, the modifications must be reflected in the adjunct schemas; otherwise, MRC and MLS functions may fail. This task is only displayed on the Database Objects menu if you have Multilingual (MLS) or Multiple Reporting Currency (MRC) functionality currently installed.

 

六、Change Maintenance Mode


1. Change Maintenance Mode

2.1.Enable Maintenance Mode

2.2.Disable Maintenance Mode

  

Thanks and Regards

学习笔记:朱龙春 - ERP DBA实践指南


ERP技术讨论群: 288307890
技术交流,技术讨论,欢迎加入
Technology Blog Created By Oracle ERP - 鲍新建
相关文章
|
3月前
|
存储 Oracle 关系型数据库
服务器数据恢复—光纤存储上oracle数据库数据恢复案例
一台光纤服务器存储上有16块FC硬盘,上层部署了Oracle数据库。服务器存储前面板2个硬盘指示灯显示异常,存储映射到linux操作系统上的卷挂载不上,业务中断。 通过storage manager查看存储状态,发现逻辑卷状态失败。再查看物理磁盘状态,发现其中一块盘报告“警告”,硬盘指示灯显示异常的2块盘报告“失败”。 将当前存储的完整日志状态备份下来,解析备份出来的存储日志并获得了关于逻辑卷结构的部分信息。
|
7月前
|
存储 Oracle 关系型数据库
【YashanDB 知识库】YMP 校验从 yashandb 同步到 oracle 的数据时,字段 timestamp(0) 出现不一致
在YMP校验过程中,从yashandb同步至Oracle的数据出现timestamp(0)字段不一致问题。原因是yashandb的timestamp(x)存储为固定6位小数,而Oracle的timestamp(0)无小数位,同步时会截断yashandb的6位小数,导致数据差异。受影响版本:yashandb 23.2.7.101、YMP 23.3.1.3、YDS联调版本。此问题会导致YMP校验数据内容不一致。
|
8月前
|
Oracle 关系型数据库 Linux
【YashanDB 知识库】通过 dblink 查询 Oracle 数据时报 YAS-07301 异常
客户在使用 YashanDB 通过 yasql 查询 Oracle 数据时,遇到 `YAS-07301 external module timeout` 异常,导致 dblink 功能无法正常使用,影响所有 YashanDB 版本。原因是操作系统资源紧张,无法 fork 新子进程。解决方法包括释放内存、停掉不必要的进程或增大进程数上限。分析发现异常源于 system() 函数调用失败,返回 -1,通常是因为 fork() 失败。未来 YashanDB 将优化日志信息以更好地诊断类似问题。
|
4月前
|
存储 Oracle 关系型数据库
oracle数据恢复—oracle数据库执行错误truncate命令的数据恢复案例
oracle数据库误执行truncate命令导致数据丢失是一种常见情况。通常情况下,oracle数据库误操作删除数据只需要通过备份恢复数据即可。也会碰到一些特殊情况,例如数据库备份无法使用或者还原报错等。下面和大家分享一例oracle数据库误执行truncate命令导致数据丢失的数据库数据恢复过程。
|
7月前
|
Oracle 关系型数据库 Java
【YashanDB知识库】Flink CDC实时同步Oracle数据到崖山
本文介绍通过Flink CDC实现Oracle数据实时同步至崖山数据库(YashanDB)的方法,支持全量与增量同步,并涵盖新增、修改和删除的DML操作。内容包括环境准备(如JDK、Flink版本等)、Oracle日志归档启用、用户权限配置、增量日志记录设置、元数据迁移、Flink安装与配置、生成Flink SQL文件、Streampark部署,以及创建和启动实时同步任务的具体步骤。适合需要跨数据库实时同步方案的技术人员参考。
【YashanDB知识库】Flink CDC实时同步Oracle数据到崖山
|
7月前
|
存储 Oracle 关系型数据库
【YashanDB 知识库】YMP 校验从 yashandb 同步到 oracle 的数据时,字段 timestamp(0) 出现不一致
【YashanDB 知识库】YMP 校验从 yashandb 同步到 oracle 的数据时,字段 timestamp(0) 出现不一致
|
7月前
|
Oracle 关系型数据库 Linux
【YashanDB知识库】通过dblink查询Oracle数据时报YAS-07301异常
【YashanDB知识库】通过dblink查询Oracle数据时报YAS-07301异常
|
8月前
|
Oracle 关系型数据库 Linux
【YashanDB 知识库】通过 dblink 查询 Oracle 数据时报 YAS-07301 异常
某客户在使用 YashanDB 通过 yasql 查询 Oracle 数据时,遇到 `YAS-07301 external module timeout` 异常,导致 dblink 功能无法正常使用,影响所有版本。问题源于操作系统资源紧张,无法 fork 新子进程。解决方法包括释放内存、停掉不必要的进程或增大进程数上限。分析发现异常原因为系统调用 fork() 失败。经验总结:优化日志记录,提供更多异常信息。
|
7月前
|
存储 Oracle 关系型数据库
【YashanDB知识库】YMP校验从yashandb同步到oracle的数据时,字段timestamp(0)出现不一致
【YashanDB知识库】YMP校验从yashandb同步到oracle的数据时,字段timestamp(0)出现不一致
|
10月前
|
存储 Oracle 关系型数据库
服务器数据恢复—华为S5300存储Oracle数据库恢复案例
服务器存储数据恢复环境: 华为S5300存储中有12块FC硬盘,其中11块硬盘作为数据盘组建了一组RAID5阵列,剩下的1块硬盘作为热备盘使用。基于RAID的LUN分配给linux操作系统使用,存放的数据主要是Oracle数据库。 服务器存储故障: RAID5阵列中1块硬盘出现故障离线,热备盘自动激活开始同步数据,在同步数据的过程中又一块硬盘离线,RAID5阵列瘫痪,上层LUN无法使用。

热门文章

最新文章

推荐镜像

更多