Unable to detect installed products please make sure that config admin xml

03.11.202321.08.2022 admin 0 Comments

Unable to detect installed products please make sure that config admin xml

Installed on the D drive, the installation file path is not Chinese, the user name is not Chinese, the stable file is also the default path, but there is still this dialog box:

And it’s weird that I can use it the night before, well, I don’t know what’s wrong.
Then when I was going to reinstall the installation package, I suddenly remembered. I changed the name of a folder in the installation path last night. Obsessive-compulsive disorder appeared from HFSS–>HFSS17 This error.
So don’t change the folder name at will after you install the software next time, don’t change the folder name at will!

Intelligent Recommendation

The problem that the container port installed by the docker installation after restarting is unable to access

question For general questions, describe: After the docker is installed in CentOS, Gitea, Siyuan, and CoderServer are installed normally; After restarting the system, go to the host to pass[IP: port]T.

Installation idea being given in ubuntu18.04: Startup Error: Unable to detect graphics environment

/Desktop# /idea/idea2019.1.3/bin/idea.sh Startup Error: Unable to detect graphics environment Solution: set the environment variable: sudo vim

/.bashrc add the following: export DI.

Mysql-python-1.2.4b4.win32.-py2.7.exe failed, unable to detect the Python installation directory

When the installation is prompted to be python2.7, but at this time python2.7 has been added to the environment variable, to solve this problem, you can use the following method: Under installation di.

Remember the unable to detect adb version of the Unable to Detect Adb Version

Unable to detect cloudera-manager-server

CDH6.2.0 installation jump pit notes During the agent installation stage on the web interface, it always prompts that cloudera-manager-server cannot be detected Solution: First determine that cloudera.

Unable to detect installed products please make sure that config admin xml

For the past few days I’ve had trouble saving the changes that I’ve make to my DEF_UI HUD. So, today I tried to reinstall the mod to see if that would fix the problem, but that only multiplied my problems. Now, not only am I unable to save the changes to my HUD, but when I log into the game I’m presented with a big red and white banner the says «Make Config XML with Config app please run HudMenuSet.exe from Data interface folder»

I’m not exactly sure what «make config XML with config app. » means. Anyone know what they’re talking about?

This problem started after I installed/uninstalled the «Functional Displays» mod, if that helps.

in data/interface there is an application called HUDMenuSet.

Run that, leaving it default if you want, then save it (Ctrl+S) to data/interface/DEF_CONF

It must be located in that folder. DEF_CONF.

in data/interface there is an application called HUDMenuSet.

Run that, leaving it default if you want, then save it (Ctrl+S) to data/interface/DEF_CONF

It must be located in that folder. DEF_CONF.

in data/interface there is an application called HUDMenuSet.

Run that, leaving it default if you want, then save it (Ctrl+S) to data/interface/DEF_CONF

It must be located in that folder. DEF_CONF.

I’ve been using DEF_UI for about 8 months without any problems. I’m aware of how to make saves. This problem started after I installed the «Functional Displays» mod, which made my game crash at the loading screen. before I disabled it.

You realize that vital information was not in the original post?

Also «make saves?» That is not how you «make saves.» That is how you make DEF_HUD’s configuration file.

Functional Displays is an ancient broken mod. Do not use mods with 53 open bug reports.

You realize that vital information was not in the original post?

Also «make saves?» That is not how you «make saves.» That is how you make DEF_HUD’s configuration file.

Functional Displays is an ancient broken mod. Do not use mods with 53 open bug reports.

Check if you have any mods which could conflict with Def_HUD like Hud Framework (never had issues with it myself), Key Nuker (already included with Def_UI) or anything else. Uninstall them and see if it solves the issue.

Or if you’re using a mod manager, they make virtual installations (at least NMM the one i’m using does it, don’t know about the others). Anyway check these virtual folders.

If you have NMM, launch it :

— click on the arrow next to the folder icon at the top and click on «Open NMM’s Mods Folder»
— look for your def_ui folder
— check if in THIS folder and especially in the «DEF_CONF» folder you have a DEF_HUD.xml.

On my end it wasn’t there, copying my custom XML from my Data/Interface/DEF_CONF to the virtual folder solved my issue. I hope this will help you or others having that problem.

If not, I have no other ideas for this.
Good luck and I hope it will work.

Unable to detect installed products please make sure that config admin xml

Installed on the D drive, the installation file path is not Chinese, the user name is not Chinese, the stable file is also the default path, but there is still this dialog box:

Intelligent Recommendation

The problem that the container port installed by the docker installation after restarting is unable to access

Installation idea being given in ubuntu18.04: Startup Error: Unable to detect graphics environment

/Desktop# /idea/idea2019.1.3/bin/idea.sh Startup Error: Unable to detect graphics environment Solution: set the environment variable: sudo vim

/.bashrc add the following: export DI.

Mysql-python-1.2.4b4.win32.-py2.7.exe failed, unable to detect the Python installation directory

Remember the unable to detect adb version of the Unable to Detect Adb Version

Unable to detect cloudera-manager-server

Ошибка получения файла config.xml

Внимание! Данный форум является модерируемым.
Для получения к нему доступа необходимо зарегистрироваться или авторизоваться на сайте.

Здравствуйте.
У пользователей при запуске 1С CRM выскакивает служебное сообщение:
ОШИБКА при синхронизации с сервером защиты
Ошибка получения файла
config.xml

Работать дальше можно, просто закрыв сообщение. Ключи CRM и Автотранспорт. Сервер защиты и управления оборудованием 1С-Рарус
Версия: 1.1.3.982

[QUOTE]Яна Заверняева пишет:
Здравствуйте.

-проходят ли ping по имени сервера? ДА, проходят, DNS работает.

Антивирус не при чем, проверялось и без него.

«Управление торговлей», редакция 10.3 (10.3.7.8)

если смотреть в оснастке панели управления «Ключи защиты»:

Версия драйвера ключа: 9.1
Версия программы: 8.0.1.75

У вас проблемы с каким решением? Управление торговлей или CRM?
Если с CRM, то требуется номер релиза CRM

версию сервера лицензирования можно посмотреть, набрав в браузере: http://localhost:11998/ (если браузер запущен на сервере)
http://IP сервера:11998/ (если смотрите с локальной машины)

Скорее всего у вас не последний релиз, по-этому советую обновить и решение и систему защиты до последнего релиза.
Также проверьте, есть ли у ВСЕХ пользователей ВСЕ права на каталог системы защиты Protect

2 Installation, Patching, and Configuration

This chapter describes issues associated with Oracle Fusion Middleware installation, patching, and configuration. It includes the following topics:

This chapter contains issues you might encounter while installing, patching, or configuring any of the Oracle Fusion Middleware products.

Be sure to review the product-specific release note chapters elsewhere in this document for any additional issues specific to the products you are using.

2.1 Installation Issues and Workarounds

This section describes issue and workarounds related to Oracle Fusion Middleware product installation. It includes the following topics:

2.1.1 Resolving PATH and Directory Issues on Windows

This section contains the following:

2.1.1.1 Oracle Universal Installer Does Not Support Spaces in Directory Paths

If you are running Oracle Universal Installer from the command line on a Windows operating system and you need to specify the location to a specific JRE, make sure there are no spaces in the directory path to the JRE that is specified as a parameter from the command line. For example, the following is not supported:

To work around this issue, you must shorten «C:\Program Files» to use the Windows short name «C:\Progra

1″ as shown below:

2.1.1.2 Setting the PATH Environment Variable to Include Directories Containing Spaces or Parentheses

If your PATH environment variable includes a directory containing spaces or parentheses (for example, C:\Program Files or C:\Program Files (x86) ), you must convert this directory to the Windows short name as specified below:

1 in your PATH environment variable.

2 in your PATH environment variable.

In addition, if your PATH environment variable includes another environment variable that uses either C:\Program Files or C:\Program Files (x86) in its definition, then you must also change C:\Program Files or C:\Program Files (x86) to its respective Windows short name in that environment variable’s definition.

2.1.1.3 Setting the PATH Environment Variable for Oracle Configuration Manager

2.1.2 Issues Pertaining to Oracle SOA Suite Installation

This section contains the following:

2.1.2.1 Installing Oracle SOA Suite on a Dual Stack Host with IPv4

If you install Oracle SOA Suite on a dual stack host and the SOA front end URL is only set to IPv4, Oracle BPM Worklist or asynchronous callbacks from IPv6-only clients may have problems resolving IPv4 callback URLs (and vice-versa).

The work around is to use either a split Domain Name System (DNS) or another forward proxy configuration. This enables the IPv6-only client to connect to a dual stack box through its IPv6 interface.

2.1.2.2 Installing Oracle SOA Suite Release 11.1.1.3.0 in a Turkish Environment

If you are installing Oracle SOA Suite Release 11.1.1.3.0 in a Turkish environment, there will be some functionality loss for Oracle Enterprise Manager Fusion Middleware Control.

There is no work around for this issue. Oracle recommends that you avoid installing in a Turkish environment and install in an English environment instead.

2.1.2.3 Prerequisite Checks Fail During the Installation of Oracle Portal, Forms, Reports, and Discoverer 11 g Release 1 (11.1.1.2.0) on OEL6

During the installation of Oracle Portal, Forms, Reports and Discoverer 11g Release 1 (11.1.1.2.0) on OEL6 operating system, prerequisite checks fail with errors.

To work around this issue, perform any one of the following steps:

Press Continue and continue with the installation.

2.1.3 Issues Pertaining to Oracle Portal, Forms, Reports and Discoverer Installation

This section contains the following:

2.1.3.1 Installing Oracle Portal, Forms, Reports and Discoverer on Windows with IPv6

If you are installing Oracle Portal, Forms, Reports and Discoverer on a Windows operating system that supports IPv6 (for example, Windows Vista or Windows 7), the components in the installation will not start if IPv6 is enabled.

Make sure that IPv6 is disabled on your Windows operating system before you install these components.

2.1.3.2 Missing Shortcuts in the Oracle Portal, Forms, Reports and Discoverer Installation

During the installation of Oracle Portal, Forms, Reports and Discoverer on any Windows operating system, if you choose to extend your domain or expand a cluster and specify a domain name other than the default «ClassicDomain,» you will see a «Missing Shortcut» error when you try to start and stop the Managed Servers.

The work around for this issue is as follows:

From the Start menu, right-click on the shortcut that generated the error message.

In the shortcut tab, go to the target node.

Change the domain name to the correct domain name.

2.1.3.3 Oracle Configuration Manager Fails During Domain Configuration of Oracle Portal, Forms, Reports, and Discoverer 11g Release 1 (11.1.1.7.0)

After upgrading Oracle Portal, Forms, Reports, and Discoverer to 11 g Release 1 (11.1.1.7.0), or after installing Oracle Portal, Forms, Reports, and Discoverer 11 g Release 1 (11.1.1.7.0), if you choose to configure Oracle Configuration Manager during domain configuration, the configuring Oracle Configuration Manager fails.

The workaround for this issue is as follows:

Navigate to the following location on your system:

Run the following commands in the Oracle Instance home:

You can choose to skip configuring Oracle Configuration Manager when you initially run the 11 g Release 1 (11.1.1.7.0) configuration wizard.

To configure Oracle Configuration Manager after configuring the domain, do the following:

Navigate to the ORACLE_HOME/ccr/bin directory on your system.

Set the variable ORACLE_CONFIG_HOME in your Oracle Instance home directory.

Run the following commands:

2.1.3.4 Considerations When Installing Oracle Portal 11 g

Before you install a new Oracle Portal, Forms, Reports, and Discoverer 11 g environment, be sure to review the following important resources:

2.1.3.5 Prerequisite Warnings During Installation

Vendor release updates cumulative patches and/or packages that may supersede our listed Oracle Fusion Middleware 11 g Release 1 prerequisites for platforms. As long as vendor approved patches and/or packages are installed, the prerequisite warnings could be ignored and the installation completed.

2.1.4 Issues Pertaining to Oracle Web Tier Installation

This section contains the following:

2.1.4.1 Oracle SOA Suite and Oracle Application Developer Must Be Installed Before Oracle Web Tier

To ensure that the oracle_common/soa/modules/commons-cli-1.1.jar oracle_common\soa\modules\commons-cli-1.1.jar file is installed properly, if you plan to associate Oracle Web Tier with an existing domain, you must install Oracle Web Tier after all other products are installed.

2.1.4.2 Re-Installing Oracle Web Cache if Double Backslashes (\\) Are Specified During Installation

During the installation of Oracle Web Tier on Microsoft Windows operating systems, if you accidentally specified an installation directory using double backslash (\\) characters, you will encounter problems when you try to start Oracle Web Cache.

The work around is to re-install Oracle Web Cache without using double backslash characters in the installation location.

2.1.4.3 Oracle Web Tier Silent Install Requires Oracle Web Cache Component Name

If you are performing a silent Oracle Web Tier installation for Oracle HTTP Server, an Oracle Web Cache component name ( WEBCACHE_COMPONENT_NAME parameter) must also be mentioned in the response file, even though Oracle Web Cache is not required for Oracle HTTP Server installation. Even though both component names are provided, as long as CONFIGURE_WEBCACHE is set to false then only Oracle HTTP Server will be installed and configured.

There is no work around for this issue.

2.1.5 Issues Pertaining to Oracle Identity Management Installation

This section contains the following:

For 11 g Release 1 (11.1.1.6.0) installation release notes, refer to the following links:

Oracle Fusion Middleware Release Notes 11 g Release 1 (11.1.1) for Microsoft Windows (32-Bit)

2.1.5.1 Setting ADR_BASE for Oracle Internet Directory on Windows 2008 R2

On Windows 2008 R2 with Service Pack operating systems, while running the Oracle Internet Directory installer or configuration tool, if you encounter issues starting of Oracle Internet Directory instance you must do the following to avoid conflicts with log file creation between the Fusion Middleware components and database components:

In the sqlnet.ora file in the TNS_ADMIN directory ( ORACLE_INSTANCE \config ) directory of the OID environment, set the ADR_BASE parameter’s value to any directory other than the Oracle home (for example, C:\temp ). If the sqlnet.ora file does not exist in the TNS_ADMIN directory, create the file and add the ADR_BASE parameter’s value as mentioned above.

2.1.5.2 WebLogic Administration Server Must Be Running When Extending Oracle Identity Management Domains

When you install Oracle Identity Management, you have several options for choosing how the Oracle Identity Management components are installed in relation to an Oracle WebLogic Server administration domain. If you select the Extend Existing Domain option on the installer’s Select Domain screen, Oracle Identity Management components are installed in an existing Oracle WebLogic Server administration domain.

To install Oracle Identity Management components in an existing administration domain using the Extend Existing Domain option, the Oracle WebLogic Administration Server instance must be running.

2.1.5.3 Extending the Schema in Oracle Internet Directory

If you have Oracle Identity Manager 11 g Release 1 (11.1.1.7.0) against Oracle Internet Directory release prior to Oracle Internet Directory 11 g Release 1 (11.1.1.6.0) through libOVD 11 g Release 1 (11.1.1.7.0) (with oamEnabled set to true and LDAPSync enabled), when you try to create a new user, the following error is displayed:

You need to extend the schema in Oracle Internet Directory that you have installed. To change the backend IDStore schema, do the following:

Create a new attribute.

Modify the existing orclIDXPerson objectclass to include orclPwdExpirationDate as an optional attribute.

You can use Oracle Directory Services Manager to connect to Oracle Internet Directory and make the schema changes.

2.1.5.4 Deinstalling a 11 g (11.1.1.7.0) Oracle Internet Directory Instance Does Not Clean Up the OID Schema

When deinstalling a configured Oracle Internet Directory instance from Oracle Identity Management 11 g (11.1.1.7.0) the file-based instance directory is removed, but the related Oracle Internet Directory instance configuration is not deleted. Hence, any future configuration adds to the instance count by including the deleted instances.

The following logic is missing from the command to remove a OID instance:

After deleting an instance and before recreating the instance run the command:

2.1.5.5 Information about the Oracle Virtual Directory Adapters

Oracle Virtual Directory adapters are not listed in the Home page.

To work around this issue on Windows operating systems, copy the jar prior to the configuration phase because it does not work if you copy it later.

2.1.5.6 Enabling the Retry Button

To retry a failed Oracle Identity Management configuration you must enable the Retry button. Check the box on the left side of the failed item to enable the Retry button.

2.1.5.7 Server Startup Failures on Linux Operating Systems

When starting the Oracle Identity Management server (Managed server or Administration server), the server may fail to start. You may see the following error:

To work around this issue, run the following command and the start he server again:

2.1.5.8 Configuring OPMN Request Port

The static ports.ini for the Oracle Identity Management 11 g Release 1 (11.1.1.7.0) installer has an OPMN request port specified. This port is not used in the Oracle Identity Management configuration and does not serve any specific functional purpose.

To configure the port you have to manually add the entry to opmn.xml after the oracle instance is provisioned.

2.1.5.9 Silent Install with Privileged Ports on Linux Operating Systems

To install and configure privileged ports in silent mode on Linux operating systems, do the following:

Complete only a silent install with Oracle Identity Management 11 g Release 1 (11.1.1.7.0).

Run the oracleroot.sh and oidroot.sh scripts in the Oracle home.

You must run these scripts as root user.

Run the following as root user:

Complete a silent configuration with the privileged ports.

2.1.5.10 JDK Installed in ORACLE_COMMON During WebTier and IDM Installation

2.1.6 Issues Pertaining to JDK and JRE Installation

This section contains the following:

2.1.6.1 Asian Characters are Not Displayed on Oracle Linux 6.1 with JDK Versions Older Than 6u30

If you are running on Oracle Linux 6.1 with JDK version older than 6u30, Chinese, Korean, and Japanese characters are not displayed in the Oracle Universal Installer.

To work around this issue, do the following:

Go to the JAVA_HOME /jre/lib directory.

Run the installer.

2.1.6.2 Specifying the JRE Location if Installing with Automatic Updates

If you are ins7talling one of the following Oracle Fusion Middleware products:

Oracle SOA Suite

Oracle WebCenter Portal

Oracle Service Bus

Oracle WebCenter Content

Oracle Data Integrator

Oracle Identity and Access Management

2.1.6.3 Upgrading Sun JDK in the Oracle Home Directory

Certain installations, including Oracle Identity Management, Oracle Portal, Forms, Reports and Discoverer, and Oracle Web Tier will install a Sun JDK in the Oracle home directory. This version of the Sun JDK may be lower in version than what is specified in the Oracle Fusion Middleware Certification Document:

This JDK is used internally and should not be used to deploy Oracle SOA, Oracle WebCenter Portal, or any custom J2EE applications.

If you want a single JDK version deployed for all types of applications, you can upgrade the Sun JDK to a higher version (as specified in the Oracle Fusion Middleware Certification document) using the following steps:

Shut down all processes.

Back up your existing JDK.

Install a new JDK in the same location as your existing JDK.

Restart all processes.

2.1.6.4 Out of Memory Errors When Using JDK 6 Update 23

If you are experiencing out-of-memory errors when using JDK 6 Update 23, consider the following.

In JDK 6 Update 23, the escape analysis feature was enabled by default.This is an optimization within the hotspot compiler, which may require an increased memory footprint. When there is very little free space in the process for additional native memory allocations, for example due to a very large Java heap, this could lead to an out of memory situation.

The workaround for this issue is to add the following JVM argument when you start your application:

2.1.7 Issues Pertaining to Oracle Universal Installer

This section contains the following:

2.1.7.1 Installer Produces Errors When Checking for Software Updates on My Oracle Support

The work around is to use the Search Local Directory for Updates option on the Install Software Update screen and select a patch that has already been downloaded and is available locally. Patches can be downloaded manually from My Oracle Support or they can be obtained from your Oracle Support representative.

2.1.7.2 Entering the Administrator Password for a Simple Oracle Business Intelligence Installation on Linux Operating Systems

If you are installing Oracle Business Intelligence on a Linux operating system, and you select Simple Install on the Select Installation Type screen, the «Password» field is inactive when you navigate to the Administrator Details screen.

2.1.7.3 Running the Installer From C:\Documents and Settings When C:\Documents Also Exists

The work around is to either remove or rename the C:\Documents directory.

2.1.8 Issues Pertaining to Database and Schema Installation

This section contains the following:

2.1.8.1 Error Encountered While Loading the Oracle Internet Directory (ODS) Schema

If you have password policy enabled at the database level on your Oracle database, you will receive the ORA-28003 error when loading the Oracle Internet Directory (ODS) schema.

To work around this issue, temporarily disable password policy, load the schema, then enable password policy again.

2.1.8.2 Setting the Correct Permission for the DBMS_REPUTIL Database Package

If you are creating the Oracle Internet Directory schemas in Oracle Database version 11.2.0.4 or later, use the following work around if you encounter an error from RCU:

Connect to the database as administrator and execute the following:

Re-start RCU and create the schema.

After the schema is successfully created, connect to the database again as administrator and execute the following:

2.1.8.3 Setting the Correct Permission for the DBMS_JOB Database Package

If you are creating the Oracle Internet Directory schema in an Oracle database using RCU, you may encounter the following error messages:

To work around this issue:

Stop RCU and drop any Oracle Internet Directory schemas already created. Refer to «Dropping Schemas» in Oracle Fusion Middleware Repository Creation Utility User’s Guide for instructions.

Log into the database using SQL*Plus and run the following command:

Run RCU again and create the schemas.

2.1.8.4 Problems with the Oracle Home Directory Being Overwritten on Windows

If you are installing Oracle Fusion Middleware on a Windows system, and that system already contains an Oracle database, then you may encounter issues where the ORACLE_HOME global environment variable used by the database is overwritten by the Oracle Fusion Middleware product installation.

2.1.8.5 Database Connection Failure During Schema Creation When Installing Oracle Internet Directory

If the installation of Oracle Internet Directory fails due to timeout or connection failure when connecting to a database for schema creation, you can try to reset the timeout parameter in the rcu.properties file. This file is located in the IDM_HOME /rcu/config \rcu\config directory-.

2.1.8.6 Command to Drop Tablespaces and Data Files Does Not Drop Data Files from the File System

On Windows operating systems, the command used to drop tablespaces and data files does not drop data files from the file system.

This is a known problem specific to Oracle databases running on Windows operating systems.

2.1.8.7 Using RCU 11g Release 1 (11.1.1.1.0) with Oracle Database 11g (11.2.0.1)

If you are using the version of RCU that is available in Oracle Fusion Middleware 11 g Release 1 (11.1.1.1.0) with Oracle Database 11 g (11.2.0.1), you will receive the following warning message:

This warning can be safely ignored and you can proceed with your RCU operations.

This warning will not appear in the version of RCU available in Oracle Fusion Middleware 11 g Release 1 (11.1.1.2.0) or later.

2.1.9 Error Messages and Exceptions Seen During Installation

This section contains the following:

2.1.9.1 Error Messages When Installing on IBM AIX 7.1

When installing Oracle Fusion Middleware 11 g products on IBM AIX 7.1, you may see the following errors during the prerequisite checking portion of the installation:

These messages can be safely ignored. Selecting Continue in the dialog box will allow the installation to proceed.

2.1.9.2 JRF Startup Class Exceptions May Appear in Oracle WebLogic Managed Server Logs After Extending Oracle Identity Management Domain

After extending an Oracle Identity Management domain, you may see exception messages related to JRF Startup Class in the managed server log files. For example:

You can safely ignore these exception messages—there is no loss in functionality.

2.1.9.3 Sun JDK and Oracle Configuration Manager Failures in the Installation Log File

These messages occur because the Sun JDK and Oracle Configuration Manager are not installed in the oracle_common directory. You can safely ignore these messages.

2.1.10 Issues Pertaining to Product Deinstallation

This section contains the following:

2.1.10.1 Proper Deinstallation for Reinstallation in the Event of a Failed Installation

In the event that an installation fails, and you want to deinstall the failed installation and then reinstall the software to the same location, you must do the following:

Make sure that all the managed servers in the failed installation are shut down. You must verify this in the Administration Console; the word «SHUTDOWN» must appear next to the managed server name.

Deinstall the binaries in the Oracle home directory using the deinstaller in the ORACLE_HOME /oui/bin \oui\bin directory.

Delete all the managed servers from the failed installation in the config.xml file by using the Administration Console or WLST.

Delete all directories in the DOMAIN_HOME /servers \servers directory:

This procedure will enable you to reinstall the software to the same location, using the same managed server names.

2.1.10.2 Verify PATH Before Starting Classic Installation on Microsoft Windows x64 (64-Bit)

Before starting Classic Application Server installation, any reference to Program Files (x86) must be removed from the PATH environment variable. On echoing PATH on the command prompt, Program Files (x86) should not be present.

2.1.10.3 Deinstallation Does Not Remove WebLogic Domains

There may be certain scenarios where you will need to remove WebLogic Domains that you have created. The Oracle Universal Installer is used to remove Oracle Instances and Oracle home directories only; it does not remove WebLogic Domains.

If you need to remove a WebLogic Domain, you must do so manually. Please refer to your Oracle WebLogic Server documentation for more information.

2.1.11 Oracle Recommends JDK Version 6 Update 29 for Oracle Service Bus 11g Release 1 (11.1.1.7.0)

Oracle Service Bus performs more slowly when running on certain versions of the Java Platform, Standard Edition Development Kit (JDK). For optimal performance, Oracle recommends using JDK version 6 update 29 with Oracle Service Bus 11 g Release 1 (11.1.1.7.0).

2.1.12 Installing Oracle Service Registry in the Same Domain as Oracle SOA Suite

When installing Oracle Service Registry 11 g in the same WebLogic Domain as Oracle SOA Suite 11 g Release 11.1.1.2.0 or Release 11.1.1.3.0, you may see the following error message on the WebLogic Server console when Oracle Service Registry is starting up:

To work around this issue:

Make sure Oracle Service Registry is installed on a different Managed Server from Oracle SOA Suite.

Download patch 9499508 and follow the instructions in the README file included with the patch:

Go to My Oracle Support.

Click on the Patches & Updates tab.

In the Patch Search area, search for patch 9499508.

Download the patch.

Edit the setDomainEnv.sh file and, for Oracle Service Registry Server, remove fabric.jar from classpath:

When installing Oracle Service Registry 11 g in the same Weblogic Domain as Oracle SOA Suite 11 g Release 11.1.1.3.0, you may see the following error message when accessing the Oracle Service Registry console:

To work around this error, edit the setDomainEnv.sh file and remove oracle.soa.fabric.jar from the classpath when running the Oracle Service Registry Managed Server. To do this:

Make a backup of the MW_HOME /user_projects/domains/ soa_domain_name /bin/setDomainEnv.sh file.

Edit the setDomainEnv.sh file and replace the following line:

with the following:

Restart the Oracle Service Registry Managed Server.

If you have multiple Oracle Service Registry Managed Servers in the domain, each Managed Server must be added to the condition. For example, if you have two Oracle Service Registry Managed Servers named WLS_OSR1 and WLS_OSR2 :

2.1.13 Problems Installing in Thai and Turkish Locales

Turkish and Thai users are recommended to install and run Oracle Fusion Middleware using the English locale. Oracle Fusion Middleware does support Turkish and Thai locales as clients.

2.1.14 Enterprise Manager Configuration Fails with Timezone Error Message

There is a problem with the timezone detection algorithm on some versions of Windows. When the database is installed on some systems that have a fresh installation of Windows, the configuration of Enterprise Manager fails with a message that indicates that an «America/Rio_Branco» timezone has been detected.

The work around is to reset the timezone to the desired value, then re-install your Oracle Fusion Middleware product.

2.2 Patching Issues and Workarounds

This section describes issue and workarounds related to Oracle Fusion Middleware product patching. It includes the following topics:

2.2.1 Applications Will Not Start After WebLogic Server is Updated

After applying the latest patches to Oracle WebLogic Server, the WL_HOME /server/lib/weblogic.policy \server\lib\weblogic.policy file must be edited to include the following entry in order for Middleware services such as Discoverer, Access Manager, and Identity Manager to start:

Replace MW_HOME with the location of your Middleware home directory.

Replace WLS with one of the following:

patch_wls1034 for WebLogic Server version 10.3.4

patch_wls1035 for WebLogic Server version 10.3.5

patch_wls1036 for WebLogic Server version 10.3.6

2.2.2 Issues Pertaining to Patching Oracle SOA Suite

This section contains the following:

2.2.2.1 Patch Set Assistant Fails When Updating the SOAINFRA Schema in SQL Server Databases

If you attempt to update the SOAINFRA schema in a Microsoft SQL Server database, then the Fusion Middleware Patch Set Assistant fails to complete the operation. This is a known issue with no current workaround. Contact Oracle Support or refer to My Oracle Support for more information:

2.2.2.2 Exception Seen When Extending Your Existing Oracle SOA Suite Domain with Oracle Business Process Management Suite

The following intermittent exception may be seen in cases where you have upgraded your Oracle SOA Suite software to release 11.1.1.3.0 with the Patch Set Installer, and are extending your existing domain to include Oracle Business Process Management Suite:

This is a harmless exception. To avoid seeing this exception, do the following:

Connect to your database as the SOA schema user.

Drop the BPM_CUBE_ROLE_FK1 constraint by executing the following:

Recreate the BPM_CUBE_ROLE_FK1 constraint by executing the following:

Restart the Oracle SOA Managed Server.

2.2.2.3 Exception Seen When Undeploying any SOA Composite with Range-Based Dimension Business Indicators

The following intermittent exception may be seen in cases where you have upgraded your Oracle SOA Suite software to release 11.1.1.3.0 with the Patch Set Installer, and have undeployed SOA composites that have range-based dimension business indicators:

This exception is harmless and can be safely ignored. To avoid seeing this exception, do the following:

Connect to your database as the SOA schema user.

Drop the BPM_CUBE_NAMETAB_RANGE_FK1 constraint by executing the following:

Recreate the BPM_CUBE_NAMETAB_RANGE_FK1 constraint by executing the following:

Restart the Oracle SOA Managed Server.

2.2.2.4 Running Oracle Business Process Management Suite with Microsoft SQL Server 2008 Database

If you have patched your existing Oracle SOA Suite installation with the Patch Set Installer to include Oracle Business Process Management Suite and you are using a Microsoft SQL Server 2008 database, the following procedure is required after you have patched your software:

In the «Connection Pools» tab, add the following property in the «Properties» section for the mds-owsm and mds-soa data sources:

2.2.2.5 Update to Oracle SOA Suite Release 11.1.1.3.0 Does Not Remove the b2b.r1ps1 Property

After you update your Release 11.1.1.2.0 software to Release 11.1.1.3.0, and login to the Oracle Enterprise Manager Console and navigate to the b2b Properties screen, the b2b.r1ps1 property (used to enable Release 11.1.1.2.0 features such as DocProvisioning and TransportCallout) is still visible. This property is removed for Release 11.1.1.3.0.

2.2.2.6 Manual Steps for Migrating Oracle UMS and Oracle MDS

If you migrate your database schemas from Release 11.1.1.1.0 to Release 11.1.1.2.0 with the BAM Alone option:

The Oracle BAM server will not start and you will receive UMS and MDS exceptions. After executing above command, if no errors are seen in the log files and if the version in schema_version_registry is changed to 11.1.1.2.0 for Oracle BAM, then the following commands must be executed to manually migrate Oracle UMS and MDS:

Then, start the Oracle BAM server after running these commands.

2.2.2.7 Monitored BPEL Processes Generate Warning Messages in Log File After Applying 11g Release 1 (11.1.1.4.0) Patch Set

If you deployed BPEL processes that are instrumented with monitors, then Oracle BAM might generate warning messages in the SOA diagnostic log file after you apply the 11g Release 1 (11.1.1.4.0) patch set.

This is because a new business indicator data object field («LATEST») was added for Oracle Fusion Middleware 11g Release 1 (11.1.1.4.0).

To avoid the warning message and to take advantage of the new data object field, redeploy the BPEL process after you apply the 11g Release 1 (11.1.1.4.0) patch set.

2.2.2.8 Oracle Rules Error in Administration Server Log Files After Patching an 11g Release 1 (11.1.1.2.0) Domain

If you are applying the latest Oracle Fusion Middleware 11 g patch set to an 11g Release 1 (11.1.1.2.0) Oracle home, then you might see the following error in the Administration Server log files:

You will see this error if deployed a Oracle SOA Suite composite application to the domain previous to applying the patch set. This because, starting with Oracle Fusion Middleware 11g Release 1 (11.1.1.3.0), the Rules library ( oracle.rules ) must be targeted to the Administration Server, as well as to the SOA managed servers.

To avoid this message:

Use the Oracle WebLogic Server Administration Console to select the oracle.rules shared library and target it to the Administration Server as well as to the SOA managed servers in the domain.

Redeploy the application to the domain using Oracle JDeveloper 11g Release 1 (11.1.1.3.0) or later.

2.2.2.9 Incorrect Instance State of Composite Applications After Applying the Latest Patch Set

If you deployed any composite applications in Oracle SOA Suite 11 g Release 1, and then you apply the latest 11 g Release 1 patch set, then you might find that the instance state of some of your composite applications appears incorrect.

For example, if any of your composite applications were in a «recovery required» state before you applied the patch set, then those composite applications may be identified as completed when you view them on the Dashboard tab of the SOA Composite page in Fusion Middleware Control.

In these cases, you can ignore the «completed» indicator. The instances are actually still running and will be treated as such by other operations, such as a purge operation.

After you install the patch set, you should analyze each of these instances to determine whether they should be completed, aborted, or left to continue.

Источники информации: