Pular para o conteúdo principal

Configure PCP - Parallel Concurrent Processing R12

1) edit context file (vi $CONTEXT_FILE):
find and change the variables:
s_appldcp to ON
s_applcsf to shared file system
s_appltmp to valid UTL_FILE_DIR  configured in database


2) Run autoconfig for all nodes


3) Check tnsnames.ora and listener.ora in $TNS_ADMIN, if exist FNDSM and FNDFS entries

4) In System Administrator Responsibility > Concurrent > Manager > Define, set primary and secundary node for all manager.

5) Set profile option 'Concurrent: PCP Instance Check' to OFF if database instance-sensitive failover is not required. By setting it to 'ON', a concurrent manager will fail over to a secondary Application tier node if the database instance to which it is connected becomes unavailable for some reason.


*** There are programs (MRP and Transaction Managers for example) that are not natively support RAC Database. Some programs use DBMS_PIPE, was therefore required specific configuration for these programs

Comentários

Postagens mais visitadas deste blog

Webcenter Content - Cache Configuration for JdbcFileStore configuration

The configuration values below, control the temporarily cached files keep in FileCache table. FsCacheThreshold Specifies the maximum cache size, in megabytes (default=100) Once the threshold is met, Content Server starts deleting files that are older than the minimum age, as specified by the FsMinimumFileCacheAge parameter FsMaximumFileCacheAge The age at which files are deleted, expressed in days. The default is 365 days FsMinimumFileCacheAge The minimum age at which cached files can be deleted This parameter is used in conjunction with the FsCacheThreshold parameter to determine when to delete cached files FsCleanUpCacheDuringIndexing This parameter activates vault cache cleaning, while FsCacheThreshold, FsMaximumFileCacheAge and FsMinimumFileCacheAge are controling its behaviour.  Expect, when this is enabled on a system that currently has a large number of files in the FileCache table, the first cycle will take a long time to complete. How to Confi...

Oracle Data Modeler and SQL Developer: change user interface (GUI) language

Oracle Data Modeler and Oracle SQL Developer does not allow to change the user interface language in “Options” or somewhere else in the GUI. This applies to the versions: Oracle SQL Developer Data Modeler - Version All and later (18.2.0 in my case) Oracle SQL Developer - Version 3.2 and later However, it’s possible switch to other language, changing datamodeler\ide\bin\ide.conf configuration file. The following lines should be added to the file for support English: AddVMOption -Duser.language=en AddVMOption -Duser.country=US Restart application! SQL Developer and Data Modeler supports the following languages: French(fr), German(de), Italian(it), Spanish(es), Brazilian Portuguese(pt BR), Japanese(ja), Korean(ko), Simplified Chinese(zh CN), Traditional Chinese(zh TW).

Recompile JSP EBS - R12.2

1. Backup $ cd $EBS_APPS_DEPLOYMENT_DIR/oacore/html/WEB-INF/classes/ $ mv _pages _pages_old 2. Stop services cd $ADMIN_SCCRIPTS_HOME ./adapcctl.sh stop ./admanagedsrvctl.sh stop oafm_server1 ./admanagedsrvctl.sh stop oacore_server1 3. Compile the jsps manually  cd $FND_TOP/patch/115/bin/ perl $FND_TOP/patch/115/bin/ojspCompile.pl --compile --flush -p             4. Checking $ cd $EBS_APPS_DEPLOYMENT_DIR/oacore/html/WEB-INF/classes/_pages $ ls -ltr  5. Start services cd $ADMIN_SCCRIPTS_HOME ./admanagedsrvctl.sh start oacore_server1 ./admanagedsrvctl.sh start oafm_server1 ./adapcctl.sh start 6. Clear your web browser cache