This is default featured slide 1 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions.This theme is Bloggerized by Lasantha Bandara - Premiumbloggertemplates.com.

This is default featured slide 2 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions.This theme is Bloggerized by Lasantha Bandara - Premiumbloggertemplates.com.

This is default featured slide 3 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions.This theme is Bloggerized by Lasantha Bandara - Premiumbloggertemplates.com.

This is default featured slide 4 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions.This theme is Bloggerized by Lasantha Bandara - Premiumbloggertemplates.com.

This is default featured slide 5 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions.This theme is Bloggerized by Lasantha Bandara - Premiumbloggertemplates.com.

Thursday, 23 June 2011

ORA-12518: TNS: listener could not hand off client connection tips

ORA-12518: TNS:listener could not hand off client connection

Cause: The process of handing off a client connection to another process failed.

Action: Turn on listener tracing and re-execute the operation. Verify that the listener and database instance are properly configured for direct handoff. If problem persists, call Oracle Support




Question:
With Oracle 10g using a Windows platform, how do I resolve ORA-12518?
Answer:
ORA-12518 is often due to network issues, and in HP-UX, there are various bugs causing ORA-12518.
In reference to your platform, there are a few resolutions that may be available for ORA-12518:
  • Try looking in the EventLog to check out network connections and associated errors, as well as the alert log in the database.  ORA-12518 can also be thrown along with a database crash.
  • Look in the windows service for your Oracle service status
    • start--->run--->services.msc
  • The server may be in need of a swap memory to disk as it runs out of memory space.  Sometimes, Oracle processes can take up alot of memory.  If you think this is causing ORA-12518 in your case, you can try this workaround:
    • set parameter to DIRECT_HANDOFF_TTC_LISTENER=OFF in listener.ora
    • restart listener
  • You may also want to consider making he large_pool_size larger.

Wednesday, 15 June 2011

How to Trace AE and COBOL Processes

For AE, Open the Process Definition under PeopleTools, Process Scheduler. Go to the override tab, and on the Parameter list line select Append from the dropdown, and in the edit box next to it, you can use the desired combination of traces, they all are; 

Parameter List Append -TRACE 7 -TOOLSTRACEPC 3596 -TOOLSTRACESQL 31 

Save the Defnition and hence forth this program will be traced each time it is run, until this is removed. Using Both the -TOOLSTRACEPC & -TOOLSTRACESQL together should only be done when required, as the output from both go into the same file, making it very large and difficult to read. For normal program tracing using just the; 

-TRACE 7 -TOOLSTRACEPC 3596 

Give the Application Engine Trace, which traces the SQL in an AE program, and the PeopleSoft Trace, which is the pcode trace. 

The above settings have equivelent settings in psprcs.cfg, they are; 

TraceAE= -TRACE output goes into Application Engine Trace (.AET) 
TracePC= -TOOLSTRACEPC output goes into the PeopleTools trace file (.trc) 
TraceSQL= -TOOLSTRACESQL output ALSO goes into the PeopleTools trace file (.trc) 

Again, depending on what the program is doing, most commnoly we'd use the -TRACE & -TOOLSTRACEPC together. The only time I use the -TOOLSTRACESQL is when we're looking for a problem with the psae program itself.

Thursday, 9 June 2011

PeopleSoft SMTP issue

While sending mail from workflow message, I was facing the issue. Appserver log says:


SendMailException: Detail Message:JavaMail Error: DNS error.\nStack Trace:\njavax.naming.CommunicationException: DNS error [Root exception is java.net.PortUnreachableException: ICMP Port Unreachable]; remaining name 'tbrl.in'
at com.sun.jndi.dns.DnsClient.query(Unknown Source)
at com.sun.jndi.dns.Resolver.query(Unknown Source)
at com.sun.jndi.dns.DnsContext.c_getAttributes(Unknown Source)
at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_getAttributes(Unknown Source)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.getAttributes(Unknown Source)
at com.sun.jndi

I turned on the SMTP trace from appserver and found the error as:

com.sun.mail.smtp.SMTPSendFailedException: 530 5.7.1 Client was not authenticated


the actual issue was with Exchange server:


You can telnet the server from you application server ans try to send the mail using command

telnet xxx.xxx.xxx.xxx 25 
EHLO <your appserver IP>   
MAIL FROM: <sender mail address>   
RCPT TO: <receipient mail address>
DATA   
Subject: Test message   


Test message body   
.   
quit




if it gives the error it means the issue is with exchange server and ask you mail admin to provide required access.


Thanks,
Praveen Joshi