正德厚生,臻于至善

Oracle EBS Applications system的维护模式

xuwanxin1987阅读(22)

       EBS维护模式是Oracle EBS应用系统 R11.5.10之后的一种新的操作模式,它限制其他用户登录任何的职责,仅供打Patch时用。这为AutoPatch会话提供了最佳的性能和减少时间需求。

1.调度系统停机时间

       管理员可以通过Oracle Applications Manager (OAM)调度'System Downtime' :

Site Map --> Maintenance --> Manage Downtime Schedules

       当系统被排入计划停机时间时,在Restricted Mode使用脚本(adaprstctl.sh)重启Apache,此时,用户登录应用系统将被重定向到系统停机URL ,可以看到类似如下的信息:

Scheduled Downtime Details
Start Time       : 17:30:00 12/11/2004
Expected Up Time : 09:00:00 12/12/2004
For Updates      : famy2u@hotmail.com
The system is currently undergoing a scheduled maintenance.
<Current Status>

This message can be customized with any text message.  If No Downtime has been specified, and the users

try to access the Applications, the following message might also appear:

! Warning
The system has not been taken off maintenance mode completely.
Please contact your System Administrator.

2.维护模式的特点

       可以在adadmin命令菜单下或Oracle Applications Manager中启用(Enabled)和禁用(Disabled)维护模式;

       在disabled的维护模式中,也可以运行AutoPatch,不过性能比较低下;

       当系统启用维护模式时,用户不能登录,会返回一个单独的访问页面,如上。

3.启用(Enabled)和禁用(Disabled)维护模式

       我们每次开始打Patch时,需要启用维护模式,打完之后需禁用维护模式。

在adadmin命令菜单下启用/禁用维护模式;

      adadmin: Options 5, 1   ---Enabled

                      Options 5, 2   ---Disabled

使用$AD_TOP/patch/115/sql/adsetmmd.sql脚本去启用维护模式;

       用adsetmmd.sql脚本是将Profile 的 'Applications Maintenance Mode' (APPS_MAINTENANCE_MODE) 选项设置为 'MAINT',而'NORMAL' 表示禁用维护模式。

可以先查询系统是否启用维护模式:

sqlplus apps/apps

SQL> select fnd_profile.value('APPS_MAINTENANCE_MODE') from dual; 

    MAINT  -   启用维护模式.
    NORMAL -   禁用维护模式.

然后使用adsetmmd.sql脚本启用/禁用维护模式:

SQL> @$AD_TOP/patch/115/sql/adsetmmd.sql  ENABLE | DISABLE

4.操作步骤:

1.  Schedule the 'System Downtime' from OAM

OAM: Site Map --> Maintenance --> Manage Downtime Schedules

At the moment of the downtime, do the following:

2.  Shutdown Apache (on Normal Mode):

   adapcctl.sh stop
   or
   adstpall.sh <apps_user>/<apps_pwd>

3.  Enable 'Maintenance Mode' from adadmin

   adadmin: Options 5, 1

4. Start Apache (on Restricted Mode)

   adaprstctl.sh start

5. Apply the Patch with adpatch
6.  Stop Apache (on Restricted Mode)

  adaprstctl.sh stop

7.  Disable 'Maintenance Mode' from adadmin

   adadmin: Options 5, 2

8.  Start Apache (on Normal Mode):

  adapcctl.sh start
  or
  adstrtal.sh <apps_user>/<apps_pwd>

pdb及pdb service自动启动

xuwanxin1987阅读(18)

alter session set container=BZUAT;
exec dbms_service.start_service('ebs_BZUAT');

alter session set container=CDB$ROOT;
alter pluggable database all open;
alter pluggable database all save state;

sqlplus / as sysdba
CREATE OR REPLACE TRIGGER open_all_pdbs
   AFTER STARTUP
   ON DATABASE
BEGIN
   EXECUTE IMMEDIATE 'alter pluggable database all open';
END open_all_pdbs;
/

sqlplus / as sysdba
alter session set container=BZUAT;
CREATE OR REPLACE TRIGGER pdb_after_startup_trg
AFTER STARTUP ON PLUGGABLE DATABASE
BEGIN
  dbms_service.start_service('ebs_BZUAT');
  NULL;
END;
/
然后每次重启的时候,可以自动启动service

Troubleshooting ADOP failures in R12.2

xuwanxin1987阅读(25)

原文链接:https://techgoeasy.com/troubleshooting-adop-failures-in-r12-2/

6.Adop apply fails with "Do you wish to apply this patch now [No]"

The following error is reported in the log file
This base patch contains files that may require translation
depending on the languages you currently have installed.
Oracle Corporation recommends that you obtain any translated versions of this
patch for each of your non-US languages after applying this base patch.
Or you may request and apply a Translation Synchronization Patch
to obtain the translation.
Do you wish to apply this patch now [No] ? No

Cause
The adalldefaults.txt was providing the default answer "No" during the patch application.
As per the following output:
$APPL_TOP/admin/${TWO_TASK}/adalldefaults.txt

Start of Defaults Record

%%START_OF_TOKEN%%
MISSING_TRANSLATED_VERSION
%%END_OF_TOKEN%%

%%START_OF_VALUE%%
No
%%END_OF_VALUE%%
End of Defaults Record

Solution
Please change the: $APPL_TOP/admin/${TWO_TASK}/adalldefaults.txt:

## Start of Defaults Record
 %%START_OF_TOKEN%%
  MISSING_TRANSLATED_VERSION
 %%END_OF_TOKEN%%

 %%START_OF_VALUE%%
Yes
 %%END_OF_VALUE%%
## End of Defaults Record

Interoperability Notes

xuwanxin1987阅读(44)

Interoperability Notes: Oracle E-Business Suite Release 12.1 with Oracle Database 19c(Doc ID 2580629.1)
Using Transportable Tablespaces to Migrate Oracle E-Business Suite Release 12.1 Using Oracle Database 19c Enterprise Edition On a Multitenant Environment(Doc ID 2707504.1)
Using Oracle E-Business Suite Release 12.1 with a Database Tier Only Platform on Oracle Database 19c(Doc ID 2640496.1)
Integrating Oracle E-Business Suite Release 12.1 with Oracle Database Vault 19c(Doc ID 2648854.1)
Oracle E-Business Suite Release 12.1: Upgrading to Oracle Database 19c with Existing Physical Standby(Doc ID 2665457.1)
Information Center: Oracle Database 19c with Oracle E-Business Suite 12.2 and 12.1(Doc ID 2655839.2)
Information Center: Oracle Database 19c with Oracle E-Business Suite 12.2 and 12.1(Doc ID 2655839.2)
Business Continuity for Oracle E-Business Suite Release 12.1 on Oracle Database 19c Using Physical Host Names(Doc ID 2567091.1)
Business Continuity for Oracle E-Business Suite Release 12.1 on Oracle Database 19c Using Logical Host Names(Doc ID 2567092.1)
Export/Import Process for Oracle E-Business Suite Release 12.1 Database Instances Using Oracle Database 19c(Doc ID 2615617.1)
Oracle E-Business Suite Release 12.1: Adding or Deleting 19c Oracle RAC Nodes(Doc ID 2617780.1)
Using Oracle 19c RAC Multitenant (Single PDB) with Oracle E-Business Suite Release 12.1(Doc ID 2530680.1)
Using utl_file_dir or Database Directories for PL/SQL File I/O in Oracle E-Business Suite Releases 12.1 and 12.2(Doc ID 2525754.1)
Interoperability Notes: Oracle E-Business Suite Release 12.2 with Oracle Database 19c(Doc ID 2552181.1)
Previous Oracle Database 19c Release Update Database Patch Lists for Oracle E-Business Suite(Doc ID 2683670.1)
Oracle E-Business Suite Releases 12.0/12.1 Technology Stack Documentation Roadmap(Doc ID 380482.1)
Deploying Oracle GoldenGate 19c to Achieve Operational Reporting for Oracle E-Business Suite Release 12 with Oracle Database 19c(Doc ID 2692032.1)
Is Oracle Database 19c Examples (Examples CD) Required for Oracle Database 19c in EBS Environment?(Doc ID 2782085.1)
Upgrading Oracle E-Business Suite Database to 19c When Integrated With Oracle Identity Management 12c(Doc ID 2817318.1)
Database Initialization Parameters for Oracle E-Business Suite Release 12(Doc ID 396009.1)

Interoperability Notes: Oracle E-Business Suite Release 12.2 with Oracle Database 19c(Doc ID 2552181.1)
Using Active Data Guard Reporting with Oracle E-Business Suite Release 12.2 and Oracle Database 19c(Doc ID 2608030.1)
Integrating Oracle E-Business Suite Release 12.2 with Oracle Database Vault 19c(Doc ID 2617770.1)
Oracle E-Business Suite Release 12.2: Upgrading to Oracle Database 19c with Existing Physical Standby(Doc ID 2665458.1)
Information Center: Oracle Database 19c with Oracle E-Business Suite 12.2 and 12.1(Doc ID 2655839.2)
Information Center: Oracle Database 19c with Oracle E-Business Suite 12.2 and 12.1(Doc ID 2655839.2)
Using Transportable Tablespaces to Migrate Oracle E-Business Suite Release 12.2 Using Oracle Database 19c Enterprise Edition On a Multitenant Environment(Doc ID 2674405.1)
Upgrading Oracle Database 12c to 19c for Oracle E-Business Suite Release 12.2 on OCI VM DB Systems(Doc ID 2714918.1)
Upgrading Oracle Database 12c to 19c with Oracle E-Business Suite Release 12.2 on Oracle Exadata Cloud Services(Doc ID 2662718.1)
Upgrading Oracle Database 11g to 19c with Oracle E-Business Suite Release 12.2 on Oracle Exadata Cloud Services(Doc ID 2567103.1)
Migrating and Upgrading Oracle Database 11g to 19c for Oracle E-Business Suite Release 12.2 on OCI VM DB Systems(Doc ID 2758991.1)
Business Continuity for Oracle E-Business Suite Release 12.2 on Oracle Database 19c Using Physical Host Names(Doc ID 2617787.1)
Business Continuity for Oracle E-Business Suite Release 12.2 on Oracle Database 19c Using Logical Host Names(Doc ID 2617788.1)
Using Oracle E-Business Suite Release 12.2 with a Database Tier Only Platform on Oracle 19c(Doc ID 2615883.1)
Export/Import Process for Oracle E-Business Suite Release 12.2 Database Instances Using Oracle Database 19c(Doc ID 2554156.1)
Oracle E-Business Suite Release 12.2: Adding or Deleting 19c Oracle RAC Nodes(Doc ID 2608028.1)
Integrating Oracle E-Business Suite Release 12.2 with Oracle Database Vault using ebs_system(Doc ID 2727580.1)
Using utl_file_dir or Database Directories for PL/SQL File I/O in Oracle E-Business Suite Releases 12.1 and 12.2(Doc ID 2525754.1)
Using Oracle 19c Oracle RAC Multitenant (Single PDB) with Oracle E-Business Suite Release 12.2(Doc ID 2530665.1)
Oracle E-Business Suite Release 12.2 Technology Stack Documentation Roadmap(Doc ID 1934915.1)

Oracle E-Business Suite Release 12 Critical Patch Update 2022

xuwanxin1987阅读(134)

Information Center: Oracle Database 19c with Oracle E-Business Suite 12.2 and 12.1 (Doc ID 2655839.2)
12.2 E-Business Suite Applications DBA Steps To Identify The Missing Patches Listed In ETCC For The Database and Middle Tier By Bug Number (Doc ID 2057925.1)
12.2 E-Business Suite Applications DBA Steps To Run The EBS Technology Code Level Checker (ETCC) (Doc ID 2008451.1)
Assistant: Download Reference for Oracle Database/GI Update, Revision, PSU, SPU(CPU), Bundle Patches, Patchsets and Base Releases (Doc ID 2118136.2)
Database Patches Required by Oracle E-Business Suite on Oracle Engineered Systems: Exadata Database Machines and SuperClusters(Doc ID 1392527.1)
Previous Oracle Database 19c Release Update Database Patch Lists for Oracle E-Business Suite(Doc ID 2683670.1)
Database Patch Set Update Overlay Patches Required for Use with PSUs and Oracle E-Business Suite (Doc ID 1147107.1)
HISTORICAL: Database Patch Set Update Overlay Patches Required for Use with PSUs and Oracle E-Business Suite (Doc ID 2056342.1)
Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes (Doc ID 1594274.1)
Oracle E-Business Suite Release 12.2: Suite-Wide Release Update Pack and AD/TXK Delta Information (Doc ID: 1583092.1)
Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2 (Doc ID 1617461.1)
How to Find E-Business Suite Patches & E-Business Suite Technology Stack Patches (Doc ID 1633974.2)
Database Initialization Parameters for Oracle E-Business Suite Release 12 (Doc ID 396009.1)
Oracle E-Business Suite Performance Best Practices (Doc ID 2528000.1)

Oracle E-Business Suite Release 12.2 Critical Patch Update Availability Document (January 2022) (Doc ID 2815550.1)

CPU January 2022

Patch 6880880: OPatch 9i, 10.1
Patch 33515361: DATABASE RELEASE UPDATE 19.14.0.0.0
Patch 33509923: GI RELEASE UPDATE 19.14.0.0.0
Patch 33561310: OJVM RELEASE UPDATE 19.14.0.0.0
Patch 33570853: EBS RELEASE 12.1 CONSOLIDATED DATABASE FIXES FOR JAN 2022
Patch 33570871: EBS RELEASE 12.2 CONSOLIDATED DATABASE FIXES FOR JAN 2022
Patch 33528262: EBS REHOSTED: 33494814 WLS PATCH SET UPDATE 10.3.6.0.220118
Patch 33570839: EBS RELEASE 12.2 CONSOLIDATED FMW FIXES FOR JAN 2022

Oracle E-Business Suite Release 12.2 Critical Patch Update Availability Document (April 2022) (Doc ID 2856621.1)

CPU April 2022

Patch 6880880: OPatch 9i, 10.1
Patch 33806152: DATABASE RELEASE UPDATE 19.15.0.0.0
Patch 33803476: GI RELEASE UPDATE 19.15.0.0.0
Patch 33808367: OJVM RELEASE UPDATE 19.15.0.0.0
EBS RELEASE 12.1 CONSOLIDATED DATABASE FIXES FOR APR 2022
Patch 33812329: EBS RELEASE 12.2 CONSOLIDATED DATABASE FIXES FOR APR 2022
Patch 33946345: EBS REHOSTED: 33791826 WLS PATCH SET UPDATE 10.3.6.0.220419
Patch 33812339: EBS RELEASE 12.2 CONSOLIDATED FMW FIXES FOR APR 2022

Interoperability Notes: Oracle E-Business Suite Release 12.1 with Oracle Database 19c (Doc ID 2580629.1)
Interoperability Notes: Oracle E-Business Suite Release 12.2 with Oracle Database 19c (Doc ID 2552181.1)
Oracle Recommended Patches — “Oracle JavaVM Component Database PSU and Update” (OJVM PSU and OJVM Update) Patches (Doc ID 1929745.1)

https://blogs.oracle.com/ebstech/post/quarterly-ebs-upgrade-recommendations

https://www.funoracleapps.com/2021/04/upgrading-oracle-ebs-12210-database.html

EBS-Linux 操作系统标准化-配置备份

xuwanxin1987阅读(30)

sudo su -
cd /home
for username in `ls -1` 'root'
do
echo '############' $username '############' >> /tmp/crontab_`hostname`_old_$(date +%F).txt
id $username  >> /tmp/crontab_`hostname`_old_$(date +%F).txt
echo 'Crontab for user: '  $username >> /tmp/crontab_`hostname`_old_$(date +%F).txt
su - $username -c 'crontab -l' >> /tmp/crontab_`hostname`_old_$(date +%F).txt
echo -e '\n\n\n' >> /tmp/crontab_`hostname`_old_$(date +%F).txt
done
cat /tmp/crontab_`hostname`_old_$(date +%F).txt
chmod 777 /tmp/crontab_`hostname`_old_$(date +%F).txt

zip -r /tmp/conf_`hostname`_old_$(date +%Y%m%d-%H%M%S).zip \
/etc/hosts                                                 \
/etc/sysctl.conf                                           \
/etc/security/limits*                                      \
/etc/passwd                                                \
/etc/group                                                 \
/etc/fstab                                                 \
/etc/resolv.conf                                           \
/etc/sysconfig/network-scripts/ifcfg-eth*                  \
/etc/sysconfig/network-scripts/route-eth*                  \
/etc/zabbix/zabbix_agentd.conf
chmod 777 /tmp/conf_*.zip

sudo su - root
echo '############ cpuinfo physical id ############' >> /tmp/hardware_`hostname`_old_$(date +%F).txt
cat /proc/cpuinfo| grep "physical id"| sort| uniq| wc -l >> /tmp/hardware_`hostname`_old_$(date +%F).txt
echo '############ cpuinfo cpu cores ############' >> /tmp/hardware_`hostname`_old_$(date +%F).txt
cat /proc/cpuinfo| grep "cpu cores"| uniq >> /tmp/hardware_`hostname`_old_$(date +%F).txt
echo '############ cpuinfo processor ############' >> /tmp/hardware_`hostname`_old_$(date +%F).txt
cat /proc/cpuinfo| grep "processor"| wc -l >> /tmp/hardware_`hostname`_old_$(date +%F).txt
echo '############ cpuinfo name ############' >> /tmp/hardware_`hostname`_old_$(date +%F).txt
cat /proc/cpuinfo | grep name | cut -f2 -d: | uniq -c >> /tmp/hardware_`hostname`_old_$(date +%F).txt
echo '############ cpuinfo siblings ############' >> /tmp/hardware_`hostname`_old_$(date +%F).txt
cat /proc/cpuinfo | grep -e "cpu cores"  -e "siblings" | sort | uniq >> /tmp/hardware_`hostname`_old_$(date +%F).txt
echo '############ free -g ############' >> /tmp/hardware_`hostname`_old_$(date +%F).txt
free -g >> /tmp/hardware_`hostname`_old_$(date +%F).txt
echo '############ system-product-name ############' >> /tmp/hardware_`hostname`_old_$(date +%F).txt
dmidecode -s system-product-name >> /tmp/hardware_`hostname`_old_$(date +%F).txt
echo '############ lscpu ############' >> /tmp/hardware_`hostname`_old_$(date +%F).txt
lscpu >> /tmp/hardware_`hostname`_old_$(date +%F).txt
echo '############ release ############' >> /tmp/hardware_`hostname`_old_$(date +%F).txt
cat /etc/redhat-release >> /tmp/hardware_`hostname`_old_$(date +%F).txt
cat /etc/oracle-release >> /tmp/hardware_`hostname`_old_$(date +%F).txt
echo '############ pvs ############' >> /tmp/hardware_`hostname`_old_$(date +%F).txt
pvs >> /tmp/hardware_`hostname`_old_$(date +%F).txt
echo '############ vgs ############' >> /tmp/hardware_`hostname`_old_$(date +%F).txt
vgs >> /tmp/hardware_`hostname`_old_$(date +%F).txt
echo '############ lvs ############' >> /tmp/hardware_`hostname`_old_$(date +%F).txt
lvs >> /tmp/hardware_`hostname`_old_$(date +%F).txt
echo '############ fdisk -l ############' >> /tmp/hardware_`hostname`_old_$(date +%F).txt
fdisk -l|grep 'Disk /dev' >> /tmp/hardware_`hostname`_old_$(date +%F).txt
echo '############ ip ad li ############' >> /tmp/hardware_`hostname`_old_$(date +%F).txt
ip ad li|grep eth >> /tmp/hardware_`hostname`_old_$(date +%F).txt
echo '############ df -h ############' >> /tmp/hardware_`hostname`_old_$(date +%F).txt
df -h >> /tmp/hardware_`hostname`_old_$(date +%F).txt
chmod 777 /tmp/hardware_`hostname`_old_$(date +%F).txt

sz /tmp/hardware_`hostname`_old_$(date +%F).txt /tmp/conf_*.zip /tmp/crontab_`hostname`_old_$(date +%F).txt

Oracle Application Technology Layer

xuwanxin1987阅读(50)

Oracle Application DBA (AD)
Oracle Application Object Library (FND)
Oracle Common Modules (AK)
Oracle Application Utilities (AU)
Oracle Alert (ALR)
Oracle Workflow (WF)
Oracle Application Framework (OAF)
Oracle XML Publisher (XML)

RHEL 7 安装oracle rac 11.2.0.4执行root.sh报错ohasd failed to start

xuwanxin1987阅读(105)

RHEL 7 安装oracle rac 11.2.0.4执行root.sh报错ohasd failed to start

报错原因:

因为RHEL 7使用systemd而不是initd运行进程和重启进程,而root.sh通过传统的initd运行ohasd进程。

解决方法:
在RHEL 7中ohasd需要被设置为一个服务,在运行脚本root.sh之前。
步骤如下:
1. 以root用户创建服务文件
touch /usr/lib/systemd/system/ohas.service
chmod 777 /usr/lib/systemd/system/ohas.service
2. 将以下内容添加到新创建的ohas.service文件中
cat /usr/lib/systemd/system/ohas.service
[Unit]
Description=Oracle High Availability Services
After=syslog.target

[Service]
ExecStart=/etc/init.d/init.ohasd run >/dev/null 2>&1 Type=simple
Restart=always

[Install]
WantedBy=multi-user.target

3. 以root用户运行下面的命令
systemctl daemon-reload
systemctl enable ohas.service
systemctl start ohas.service
4. 查看运行状态
systemctl status ohas.service

服务起来后再运行root.sh
如果还是报ohasd failed to start错误,可能是root.sh脚本创建了init.ohasd之后,ohas.service没有马上启动,解决方法参考以下:
当运行root.sh时,一直刷新/etc/init.d ,直到出现 init.ohasd 文件,马上手动启动ohas.service,服务命令:systemctl start ohas.service

使用apps修改web登陆最终用户密码为随机8位密码(除SYSADMIN,SETUP,ASADMIN外)--生产环境禁止执行

xuwanxin1987阅读(87)

DECLARE
   l_dbname varchar2(20);
   P_INIT_PASSWORD VARCHAR2(30);
   l_change_flag VARCHAR2(10);
   l_reason varchar2(2000);
BEGIN
   select name into l_dbname from v$database;
   if l_dbname not like '%PROD' then
      update fnd_user f set f.user_guid=''  where f.user_guid is not null;
      commit;
      for rec in (select user_name from fnd_user f where f.user_id > 1110 and f.user_name not in ('SYSADMIN','SETUP','ASADMIN'))
        loop
           select dbms_random.string('x',8) into P_INIT_PASSWORD from dual;
           l_change_flag := fnd_web_sec.change_password(rec.user_name,P_INIT_PASSWORD);
           IF L_change_FLAG = 'Y' THEN  
              COMMIT;
              DBMS_OUTPUT.PUT_LINE('成功初始化用户('||rec.user_name||')的密码为:'||P_INIT_PASSWORD);
           ELSE
              rollback;
              l_reason := fnd_message.get;
              fnd_message.set_name('FND', 'FND_CHANGE_PASSWORD_FAILED');
              fnd_message.set_token('USER_NAME', rec.user_name);
              fnd_message.set_token('REASON', l_reason);
              app_exception.raise_exception;
           END IF;
        end loop;
   end if;
END;
/

frmcmp_batch.sh

xuwanxin1987阅读(127)

vi $ORACLE_HOME/bin/frmcmp_batch.sh
  #TNS_ADMIN=$ORACLE_HOME/network/admin
  TNS_ADMIN=${TNS_ADMIN:-$ORACLE_HOME/network/admin}
  export TNS_ADMIN
  
cd $AU_TOP/forms/ZHS/
frmcmp_batch.sh module=$AU_TOP/forms/ZHS/CUXGMEIMPCONFIRM.fmb userid=apps/apps output_file=$CUX_TOP/forms/ZHS/CUXGMEIMPCONFIRM.fmx module_type=form compile_all=special 
frmcmp_batch.sh module=$AU_TOP/forms/ZHS/CUXGMEIMPCONFIRM.fmb userid=apps/apps output_file=$CUX_TOP/forms/US/CUXGMEIMPCONFIRM.fmx module_type=form compile_all=special 

联系我们