الاخوة الكرام السلام عليكم ورحمة الله وبركاته
كل عام انتم بخير وتقبل الله الصيام والقيام
عند تنصيب الاوراكل 10g على جهاز windows xp sp2

بمعنى انك نصبت الوندوز وبعد ذلك نصبت sp2 وحاولت تنصب الاوركل بتظهر لك الكثير من الاخطاء
وما بتقدر تتصل بالاوراكل .
الحل تنصب الاوراكل على xp sp1

وبعد ذلك تنصب sp2

و الافضل تخليه على sp1 مع عمل تحديث متواصل للوندوز
هذا للعلم فقط لاني وجهت المشكله مع sp2
واللي عنده معلومه لا يبخل علينا
مع الشكر

Oracle Database Support for Windows XP with Service Pack 2

PURPOSE


This article is to explain the installation and post-installation issues of Oracle Database on Windows XP Service Pack 2. For other Oracle products, please see <Note:280874.1> "Oracle Products Certified for Windows XP Service Pack 2".

SUMMARY

Oracle Database 10g and Oracle9i on Windows XP are fully certified and supported when Windows XP Service Pack 2 is installed. In addition, those Oracle8i client components that are supported on Windows XP are also supported when Service Pack 2 is installed. As of the date of this note, no known code issues with these Oracle products have been identified when running on Service Pack 2. As such, no patches have been or are planned to be released by Oracle as a result of the release of Service Pack 2.
However, depending upon usage scenarios and installed products, there may need to be post-installation configuration performed in order for Oracle products to be functional on Windows XP with Service Pack 2.
The rest of this note describes installation differences and post-installation configuration steps that may need to be followed when running on Windows XP with Service Pack 2.


DETAILS


The release of Service Pack 2 for Windows XP brings a variety of changes to the Windows platform when compared with previous Windows XP releases. In particular, Windows Firewall is now enabled by default, various Internet Explorer security features have been added or hardened, Windows Remote Procedure Call (RPC) restrictions have been added, and certain memory areas are now prevented from containing executable code.
Of all the changes in Service Pack 2, the major one that affects Oracle database software concerns the default enabling of Windows Firewall after Service Pack 2 is installed. In particular, if Service Pack 2 is installed on a Windows XP machine that is being used as an Oracle database server, then the Oracle software will not be able to accept incoming client connections from other machines until the Windows Firewall is configured appropriately. In addition, a separate issue with Oracle XML DB arises because of a change in the default behavior of the WebDAV protocol in Service Pack 2, which is described later.
The rest of this document will detail the general troubleshooting and configuration tasks necessary to successfully run an Oracle database on Windows XP with Service Pack 2 installed..
INSTALLATION ISSUES
During an installation of Oracle database software, Windows may present up to three dialog boxes to the user, asking if "java.exe", "javaw.exe", or "apache.exe" should be allowed to listen on network ports and if an exception should be created for those executables. It is neither necessary nor recommended that these exceptions be created during the install since a successful install will occur even if the firewall is not opened for these executables.
No other installation behavior changes will be noticed during Oracle database software installation as a result of Windows XP Service Pack 2.
WINDOWS FIREWALL
By default, all installations of Service Pack 2 for Windows XP enable the Windows Firewall such that virtually all TCP network ports are blocked to incoming connections. As a result, any Oracle products that listen for incoming connections on a TCP port will not receive any of those connection requests and the clients making those connections will report errors.
In order to enable Oracle software to be able to accept connection requests, Windows Firewall needs to be configured by either opening up specific static TCP ports in the firewall or by creating exceptions for specific executables such that they are able to receive connection requests on any ports they choose. This firewall configuration can either be done via the Windows Firewall icon in Control Panel via the Exceptions tab or from the command line via the 'netsh firewall add ...' command. In addition, Windows will also inform the user if foreground applications are attempting to listen on a port, and if so, if the user wishes to create an exception for that executable at that time. If the user chooses to do so, the effect is the same as creating an exception for the executable either via Control Panel or from the command line.
POST-INSTALLATION CONFIGURATION
Post-installation configuration for the Windows Firewall must be undertaken if all of the following conditions are met:

1) Oracle server-side components are installed on a Windows XP machine. This would include the Oracle Database, network listeners, or any Web servers or services.

2) The Windows XP machine in question is being used as a ?server? machine and will be servicing connections from other machines over the network. If no other machines will be connecting to the Windows XP machine with the Oracle software, then no post-installation configuration steps are required and the Oracle software will function as expected.

3) The Windows XP machine in question is configured to run the Windows Firewall. If the Windows Firewall is not enabled, then no post-installation configuration steps are required
If all of the above conditions are met, then the Windows Firewall will need to be configured to allow successful incoming connections to Oracle software. In particular, depending upon the Oracle software installed and the configuration that is to be used, the Windows Firewall will need to be configured to either allow certain static ports to be opened or certain executables to be granted firewall exceptions. This configuration can either be done via the Windows Firewall icon in Control Panel or via 'netsh firewall add....'.
The following section lists the Oracle Database 10g and Oracle9i executables that listen on TCP ports on Windows, along with a brief description of the executable. It is recommended that the following executables (if in use and accepting connections from a remote, client machine) be added to the exceptions list for the Windows Firewall to ensure correct operation. All executables can be found in %ORACLE_HOME%\bin, except where noted. In addition, if multiple Oracle homes are in use, firewall exceptions may need to be created for the same executable (i.e java.exe) several times...once for each home from which that executable loads.
Since only Oracle8i client (not server) components are supported on Windows XP, there are no firewall issues when using this software after Service Pack 2 is installed.
For basic database operation and connectivity from remote clients (i.e. SQL*Plus, OCI/ODBC/OLE DB applications, etc.), the following executables need to be added to the Windows Firewall exception list:
oracle.exe - Oracle Database executable
tnslsnr.exe - Oracle TNS Listener
For remote monitoring capabilities to be available for a database running on Windows XP Service Pack 2, the following executables need to be added to the Windows Firewall exception list:
emagent.exe - Oracle Database Control (10g only)
%ORACLE_HOME%\jdk\bin\java.exe - Java Virtual Machine (10g only)
dbsnmp.exe - Oracle Agent (9i only)
After installing the Oracle Database 10g Companion CD, the following executables need to be added to the Windows Firewall exception list:
%ORACLE_HOME%\apache\apache\apache.exe - Apache Web Server
%ORACLE_HOME%\opmn\bin\opmn.exe - Oracle Process Manager
%ORACLE_HOME%\jdk\bin\java.exe - Java Virtual Machine
In order to successfully use iSQL*Plus against a database running on Windows XP with Service Pack 2, the following executables need to be added to the Windows Firewall exception list:
%ORACLE_HOME%\jdk\bin\java.exe -- Java Virtual Machine (10g only) %ORACLE_HOME%\apache\apache\apache.exe -- Apache Web Server (9i only)
Oracle Ultra Search uses the Java RMI framework to launch a remote crawler. Consequently, if the Ultra Search remote crawler feature is being used, and if the remote crawler is run on Windows XP with Service Pack 2, the following executables need to be added to the Windows Firewall exception list:
%ORACLE_HOME%\jdk\bin\rmiregistry.exe -- RMI registry application %ORACLE_HOME%\jdk\bin\rmid.exe -- RMI daemon executable
The following executables provide additional features. If these features are in use in an installation, then the corresponding executable must be added to the Windows Firewall Exception list:
dgmgrl.exe - Data Guard Manager
omtsreco.exe - Oracle services for Microsoft Transaction Server
tg4sybs.exe - Oracle Transparent Gateway for SYBASE
tg4tera.exe - Oracle Transparent Gateway for Teradata
tg4msql.exe - Oracle Transparent Gateway for MS-SQL server
tg4drsrv.exe - Oracle Transparent Gateway for DRDA
pg4arv.exe or pg4t4ic.exe - Oracle Procedural Gateway for APPC
pg4mqs92.exe or pg4mqc92.exe - Oracle Procedural Gateway for IBM MQseries
hdodbc.exe - Generic Connectivity (ODBC support going out of the database)
hsots.exe - Oracle RDBMS/transaction service (used by some Oracle iAS components)
extproc.exe - External Procedure calls
oidldapd.exe - Oracle Internet Directory LDAP Server
ORACLE XML DB
When machines with Windows XP Service Pack 2 attempt to access an Oracle XML DB repository using the HTTP/Web Distributed Authoring and Versioning (WebDAV) protocol from Windows Explorer (or other tools), a behavior change will be noticed when compared to non-SP2 installations.
Because of a security change in the WebDAV configuration in Windows XP Service Pack 2, in order for Oracle XML DB to be accessed from a client machine via the WebDAV protocol, the following must be performed:

1) Create the following registry key on the client machine and set it to a non-zero value:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters\UseBasicAuth(DWORD)

2) Either reboot the client machine or stop and restart the WebClient service.
Without this change to the registry, users may experience an error with the following text when attempting to access resources in an XML DB repository:
"The folder you entered does not appear to be valid. Please choose another."
A future release of Oracle XML DB will not require the above registry modification and will support secure protocols in addition to BasicAuth.
For more information on the WebDAV security change in Service Pack 2, go to http://www.microsoft.com/technet/prodtechn...ion129121120120
TROUBLESHOOTING
If certain connections are still unable to be successfully established even after granting exceptions to the executables listed above, the following steps can be taken to troubleshoot the installation:

1. Refer to the document available for download at the following URL to get information on Windows Firewall troubleshooting: http://www.microsoft.com/downloads/details...d-4617-bf68-f05

2. Refer to the following Microsoft Knowledge Base article to get Windows Firewall configuration information: http://support.microsoft.com/default.aspx?...kb;en-us;875357

3. Examine Oracle configuration files such as *.conf files, the Oracle key in the Windows Registry and network configuration files in %ORACLE_HOME%\network\admin. In particular, any executable listed in %ORACLE_HOME%\network\admin\listener.ora in a PROGRAM= clause must be granted an exception in the Windows Firewall since a connection can be made through the TNS Listener to that executable.

4. Look through Oracle trace files, log files, and other sources of diagnostic information for details on failed connection attempts. In particular, log and trace files on the database client machine may contain useful error codes or troubleshooting information for failed connection attempts. On the server machine, the Windows Firewall log file may contain useful information, as well.
If the above troubleshooting steps are insufficient to resolve a specific configuration issue on Windows XP Service Pack 2, the output from the "netsh firewall show state verbose=enable" command should be provided to Oracle Support for diagnosis and problem resolution.

المصدر metalink

يعطيك العافية
اخوي ابو صالح على المعلومات القيمة
وجزاك الله الف خير

الف شكر

بسم الله الرحمن الرحيم

الف الف الف شكر وجزاك اللة كل خير

اخواني من طح الموضوع فله اجره ومن اجاب فله اجره
وشكرا لكم
وجزاكم الله خيرا

السلام عليكم

لو نزلت الاوركل 10 وبعد ذلك قمت بتنصيب SP2
وبعدها Developer Suite

هل توجد مشكلة ام لأ

او اقوم بتحميل Developer Suite وبعدها SP2

افيدوني

جزاك الله خيرا