Oracle SOA: Install with error RCU-6107 DB Init Param Prerequisite failure for processes current value

If you have this error:

RCU-6107 DB Init Param Prerequisite failure for processes current value

1. Connect to the database and open SQL*plus
run: SQL> alter system set processes=300 scope=spfile;

2. find a file name: init.ora under "spfile" folder, Change parameter open_cursors=500
and find the config/scripts/initXEtemp.ora , Change parameter open_cursors=500

Weblogic: heap size

Change file setting on C:\Oracle\Middleware\jdeveloper\jdev\bin\jdev.conf
Or just find the file in JDeveloper folder.

DB2: View lock on table and kill session

get snapshot for locks on

LIST APPLICATION

FORCE APPLICATION (13347)

13347 is Application ID.

Connect EJB from other client to Weblogic

Please include following JAR file:
Creating a wlfullclient.jar for JDK 1.6 client applications
Use the following steps to create a wlfullclient.jar file for a JDK 1.6 client application:

Change directories to the server/lib directory.
cd WL_HOME/server/lib
Use the following command to create wlfullclient.jar in the server/lib directory:
java -jar wljarbuilder.jar
You can now copy and bundle the wlfullclient.jar with client applications.
Add the wlfullclient.jar to the client application’s classpath.

Creating a wlfullclient5.jar for JDK 1.5 client applications
Change directories to the server/lib directory.
cd WL_HOME/server/lib
Use the following command to create wlfullclient.jar in the server/lib directory:
java -jar wljarbuilder.jar -profile wlfullclient5
You can now copy and bundle the wlfullclient5.jar with client applications.
Add the wlfullclient5.jar to the client application’s classpath..
(REMEMBER: USE JDK1.5 to generate the jar file)

Refer from http://download.oracle.com/docs/cd/E12840_01/wls/docs103/client/jarbuilder.html#wp1077742

Default URL and username for JDeveloper Integrated Weblogic Server

Here it is:
URL: http://localhost:7101/console
username: weblogic
password: weblogic1

Oracle 11g: Error on Start up

If you get Error like:
Failed to auto-start Oracle Net Listener using xxxxx
or
ORACLE_HOME_LISTNER is not SET, unable to auto-stop Oracle Net Listener

SOLUTION:
Update file "dbstart", change link ORACLE_HOME_LISTENER=$1 to ORACLE_HOME_LISTENER=$ORACLE_HOME

DB2: Select table Primary key and Foreign Key

Primary key

SELECT NAME
FROM
SYSIBM.SYSCOLUMNS
WHERE TBNAME = 'table name'
AND TBCREATOR = 'creator'
AND KEYSEQ > 0
ORDER BY KEYSEQ ASC

Foreign Key

SELECT B.REFTBNAME AS PARENTTABLE,COLNAME
FROM
SYSIBM.SYSFOREIGN KEYS A,
SYSIBM.SYSRELS B
WHERE A.RELNAME = B.RELNAME
AND B.TBNAME = 'table name'
AND B.REFTBCREATOR = 'creator'
AND B.REFTBCREATOR = A.CREATOR

SQL: not match from table 1

SELECT TestTable1.ID, TestTable1.Name, TestTable1.Title
FROM TestTable1 LEFT JOIN TestTable ON TestTable1.[Name] = TestTable.[Name]
WHERE (((TestTable.Name) Is Null));

SharePoint: The trial period for this product has expired.

Method 1:
Go to: http://support.microsoft.com/kb/971620/en-us
(When you install the 2007 Microsoft Office servers Service Pack 2, the product expiration date is activated incorrectly) and follow the document.

Method 2:
Added application pool Account ("dcomcnfg.exe") to the Distributed users
(Add the Application Pool account to the built-in Active Directory group "Distributed COM Users".)
1. Go to Application Pool and see what's the account which can access this Application pool.
2. Go to Active Directory and find the group named "Distributed COM Users". Add the application pool account to that group.

JAVA Memory Leak

FINDING MEMORY LEAKS IN JAVA APPS

Here is a small HOWTO on how to find memory leaks with Java SE.

I’ve written it while trying to find memory leaks in our testing tools: JTHarness and ME Framework, and then wanted to share the HOWTO with the world, but I didn’t have my blog at that time, so I posted this info as a comment to a relevant entry in the excellent Adam Bien’s blog.

Note: Use the latest JDK 6, because it has the latest tools, with lots of bug fixes and improvements. All the later examples assume that JDK6’s bin directory is in the PATH.

STEP 1. START THE APPLICATION.

Start the application as you usually do:

java -jar java_app.jar

Alternatively, you could start java with hprof agent. Java will run slower, but the huge benefit of this approach is that the stack traces for created objects will be available which improves memory leak analysis greatly:

 java   -Dcom.sun.management.jmxremote   -Dcom.sun.management.jmxremote.port=9000   -Dcom.sun.management.jmxremote.authenticate=false   -Dcom.sun.management.jmxremote.ssl=false   -agentlib:hprof=heap=dump,file=/tmp/hprof.bin,    format=b,depth=10   -jar java_app.jar

When the application is up, perform various actions that you think might lead to memory leaks.

For example, if you open some documents in your app, the memory graph could rapidly go up. If closing the docs and invocation of full garbage collection did not bring the memory back to normal level, there is probably a leak somewhere.You might use jconsole from JDK 6 to see the memory consumption graph to have a clue whether memory leak is present or not:

jconsole

It will pop up a dialog with a list of Java applications to connect to. Find the one with java_app.jar and connect. Also, jconsole allows to invoke full GC providing nice button just for that.

STEP 2. FIND THE APPLICATION PID.

Find out the application’s process id via:

jps

It will print something like:

15976 java_app.jar
7586 startup.jar
22476 Jps
12248 Main
5437 Bootstrap

In our case the pid is 15976.

STEP 3. DUMP THE HEAP INTO FILE.

Dump heap into the file:

jmap -dump:format=b,file=/tmp/java_app-heap.bin 15976

We just told jmap to dump the heap into /tmp/java_app-heap.bin file, in binary from (which is optimized to work with large heaps). The third parameter is the pid we found in Step 2.

Alternatively, if you started java with hprof agent, you could just use Ctrl-\ on Solaris/Linux or Ctrl-Break on Windows to dump heap into the file, specified in hprof agent arguments.

STEP 4. VISUALIZE THE HEAP.

Use jhat tool to visualize the heap:

jhat -J-Xmx326m /tmp/java_app-heap.bin

Jhat will parse the heap dump and start a web server at port 7000. Connect to Jhat server by pointing your browser to:

http://localhost:7000

And start investigating.

Jhat allows you to see what objects are present in the heap, who has references to those objects, etc.

Here are some tips:

• Investigate _instances_, not _classes_.
• Use the following URL to see the instances: http://localhost:7000/showInstanceCounts/
• Use “Reference Chains from Rootset” (Exclude weak refs!!!) to see who’s holding the instance.

This entry was posted on Monday, April 2nd, 2007 at 1:56 am and is filed under Java. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, ortrackback from your own site.

FROM: http://blog.emptyway.com/2007/04/02/finding-memory-leaks-in-java-apps/