Problem:
After creating an spfile on an 11g instance (11.1.0.7) on R12.1.3 on Windows 2008, it does not automatically appear when the ‘show parameter spfile’ command is issued in SQL*Plus.
Solution:
When the database is started via the Windows Services panel, it seems that the pfile is used by default, even though the spfile may have been created. Stop and start the database via SQL*Plus to see the spfile.
Problem:
While backing up DEV1 instance on Windows 2008, the following error appears:
C:oracleDEV1instappsDEV1_ittl-hrmstestappltmpOFF446.tmp
Sharing violation
Solution:
Ensure that the Oracle processes are stopped in Windows Services.
It appears that there are still (orphan) database processes running. Right click the Taskbar and open Task Manager. Select the Processes tab. From the View menu, click Select columns. In Select Process Page Columns, scroll down the list and check Command Line. Delete any processes that start with C:oracleDEV1.
Step 1: Stop all Oracle processes and the Distributed Transaction Coordinator service.
Step 2: Run regedit and delete the following entries:
HKEY_LOCAL_MACHINESOFTWAREORACLE HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesOracle* HKEY_LOCAL_MACHINESYSTEMControlSet001ServicesOracle* HKEY_LOCAL_MACHINESYSTEMControlSet003ServicesOracle*
Exit regedit, and then reboot.
Step 3:Delete the Oracle directory (x:oracleVIS12) and C:Program Filesoracle.
Empty the recycle bin, and then reboot the computer once more.
Step 4:Clean up the Program Menu for Oracle entries
Step 5:Run Rapid Wizard to restart the R12 installation.
Metalink Reference:
Doc ID: 567507.1 (How to Remove an Oracle E-Business Suite Release 12.x Windows Environment)
Problem:
How can PeopleSoft profiles (fsdmo) that use BEA WebLogic as the web server be installed as a Windows Service?
Solution:
Navigate to the WebLogic domain directory (E:PSOFTFS900webservfsdmobin) and run installNTservice.cmd .
To uninstall, use UninstallNTservice.cmd :
Cd /d E:PSOFTFS900webservfsdmobin UninstallNTservice.cmd PIA UninstallNTservice.cmd WebLogicAdmin E:PSOFTFS900webservfsdmobin>UninstallNTservice.cmd PIA fsdmo-PIA removed. Press any key to continue . . . E:PSOFTFS900webservfsdmobin> E:PSOFTFS900webservfsdmobin>UninstallNTservice.cmd WebLogicAdmin fsdmo-WebLogicAdmin removed. Press any key to continue . . . E:PSOFTFS900webservfsdmobin>
Problem:
If the user that starts the IBM WebSphere web server logs off the system, the web server is shut down. A Windows service must be created to ensure that the web service(s) remain running.
Solution:
At Command Prompt, issue the following commands:
E: cd E:IBMWebSphereAppServerbin WASService.exe -add fsdev -serverName server1 -wasHome E:IBMWebSphereAppServer -profilePath E:PSOFTFS900webservfsdev -logFile E:IBMWebSphereAppServerlogsstartNodefsdev.log -restart true -startType automatic WASService.exe -add fsdmo -serverName server1 -wasHome E:IBMWebSphereAppServer -profilePath E:PSOFTFS900webservPIA_fsdmo -logFile E:IBMWebSphereAppServerlogsstartNodefsdmo.log -restart true -startType automatic E:IBMWebSphereAppServerbin>cd E:IBMWebSphereAppServerbin E:IBMWebSphereAppServerbin>WASService.exe -add fsdev -serverName server1 -wasHome E:IBMWebSphereAppServer -profilePath E:PSOFTFS900webservfsdev -logFile E:IBMWebSphereAppServerlogsstartNodefsdev.log -restart true –startType automatic Adding Service: fsdev Config Root: E:PSOFTFS900webservfsdevconfig Server Name: server1 Profile Path: E:PSOFTFS900webservfsdev Was Home: E:IBMWebSphereAppServer Start Args: Restart: 1 IBM WebSphere Application Server V6.1 - fsdev service successfully added. E:IBMWebSphereAppServerbin> The “IBM WebSphere Application Server V6.1 – fsdev” service is created. Note that the log file is E:IBMWebSphereAppServerlogsstartNodefsdev.log E:>E: E:>cd E:IBMWebSphereAppServerbin E:IBMWebSphereAppServerbin>WASService.exe -add tramdmo -serverName server1 -wasHome E:IBMWebSphereAppServer -profilePath E:PSOFTFS900webservPIA_tramdmo -logFile E:IBMWebSphereAppServerlogsstartNodetramdmo.log -restart true -startType automatic Adding Service: tramdmo Config Root: E:PSOFTFS900webservPIA_tramdmoconfig Server Name: server1 Profile Path: E:PSOFTFS900webservPIA_tramdmo Was Home: E:IBMWebSphereAppServer Start Args: Restart: 1 IBM WebSphere Application Server V6.1 - tramdmo service successfully added. To remove the service: cd E:IBMWebSphereAppServerbin WASService.exe -remove tramdmo E:>E: E:>cd E:IBMWebSphereAppServerbin E:IBMWebSphereAppServerbin>WASService.exe -add peoplebooks -serverName server1 -wasHome E:IBMWebSphereAppServer -profilePath E:PSOFTFS900webservPSOL_fsdmo -logFile E:IBMWebSphereAppServerlogsstartNodepeoplebooks.log -restart true -startType automatic Adding Service: peoplebooks Config Root: E:PSOFTFS900webservPSOL_fsdmoconfig Server Name: server1 Profile Path: E:PSOFTFS900webservPSOL_fsdmo Was Home: E:IBMWebSphereAppServer Start Args: Restart: 1 IBM WebSphere Application Server V6.1 - peoplebooks service successfully added. E:IBMWebSphereAppServerbin> To remove the service: cd E:IBMWebSphereAppServerbin WASService.exe -remove peoplebooks
Reference:
http://handly.blogspot.com/2008/05/setting-up-websphere-61-cluster-to.html
Setting up the WebSphere Node Manager as a Windows service
First, you need to set up the Node Manager on each physical server to run as a service and restart after a reboot:
Open a Command Window and go to the ..IBMWebSphereAppServerbin directory
Type in the following command (adjusted for your install paths):
WASService -add “IBM WebSphere Node Agent” -servername nodeagent -profilePath D:IBMWebSphereAppServerprofilesAppSrv01 -wasHome D:IBMWebsphereAppserver -logFile D:IBMWebSphereAppServerprofilesAppSrv01logsnodeagentstartNode.log -logRoot D:IBMWebSphereAppServerprofilesAppSrv01logsnodeagent -restart true -startType automatic
When connecting to SQL Server database using SQL Server Management Studio, the following error appears:
TITLE: Microsoft SQL Server Management Studio
——————————
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=2&LinkId=20476
——————————
BUTTONS:
OK
——————————
Solution:
The SQL Server instance service (MSSQLSERVER) is not started. Start the service using the Control Panel Services panel, or use SQL Server Configuration Manager:
SQL Server Configuration Manager (Local) > SQL Server 2005 Services > SQL Server (MSSQLSERVER)
No connection could be made because the target machine actively refused it
Problem:
When logging on to VP1, the following error appears:
File: SQL Access ManagerSQL error. Stmt #: 2 Error Position: 0 Return: 404 – [Microsoft][SQL Native Client]TCP Provider: No connection could be made because the target machine actively refused it.
Solution:
The MSSQLSERVER service was shut down on the database node. Restart it, and then log on to PeopleSoft.
1) Update the configuration.properties file.
2) Open Command Prompt, navigate to PS_HOMEbinclientwinx86 and enter:
PSEMAgentService /install PS_HOMEPSEMAgent
3) In Control Panel > Administrative Tools > Services, a new service called PeopleSoft Environment Management Agent-8.46.xx appears.
4) Adjust the logon parameters by right-clicking the service and choosing Properties.
5) To uninstall the service, open Command Prompt and type:
PSEMAgentService /uninstall
Reference:
http://www.erpassociates.com/peoplesoft-corner-wiki/peoplesoft-administration/change-assistant.html
While creating a new vendor in Oracle Applications, the following error appeared:
APP-10000: ORA-12500: TNS:listener failed to start a dedicated server process
ORA-06512: at "PO.API_PUT_ERROR_SP", line 9
ORA-06512: at "PO.API_POVNDHDR_TRG", line 208
ORA-12500: TNS:listener failed to start a dedicated server pricess
ORA-04088: error during execution of trigger 'PO.API_POVNDHDR_TRG' occurred in AP_VENDORS_PKG.INSERT_ROW<-APXVDMVD with parameters (ROWID = , VENDOR_ID = 10282) while performing the following operation:
Insert into PO_VENDORS
The following steps were taken to troubleshoot the issue:
1. Ensured the respective Oracle services were running properly (OracleServicePROD, OracleStartPROD, the Concurrent Manager and TNS Listener) by stopping and restarting them.
2. Obtained TNS-12500 troubleshooting document from Oracle’s Metalink website and ensured that all items on the list were resolved.
3. Checked the Event Log on EWSD1PROD for error messages.
4. Checked Oracle’s ALERT.LOG file on ORA errors messages.
5. Ran ScanDisk on the E: of the EWSD1PROD (Oracle Financials) server.
6. Checked the SQL code in the procedure “PO.API_PUT_ERROR_SP”, which appeared in the error message. This showed that the procedure was attempting to access the MAXIMO instance.
7. Completed the backup on MAXIMO and allowed the Oracle database services on the MAXIMO server to restart.
Solution: Transactions were being pushed from Oracle Applications to the MAXIMO server, which had been shut down. Upon restarting MAXIMO server, the issue was resolved.
Problem: After installing a fresh instance, when Active Users report is run, it exits with error.
Solution: Run ccmsetup. Delete the concurrent manager service, then add back service. Remember to set apps password, database sid and Automatic checkbox. Reboot the computer.
Recent Comments