CategoryErrors

Steps to configure Weblogic proxy plugin in IIS6.0

To configure weblogic Proxy plugin in IIS6.0 we need to have mainly two dll’s (iisforward.dll & iisproxy.dll) and iisproxy.ini in the same folder. The mentioned dll’s  (iisforward.dll & iisproxy.dll) are available with the weblogic installation folder.

My environment details

Microsoft windows server 2003(32bit)
IIS6.0
Weblogic 10.3.6

In my setup the dll’s was available in the below location for WL 10.3.6  C:OracleMiddlewarewlserver_10.3serverpluginwin32

Copy the iisforward.dll, proxy.dll to C:Inetpubwwwroot and create a file iisproxy.ini with the below simple configuration.

WebLogicHost=<Weblogic host>
 WebLogicPort=7001
 WlForwardPath=/
 Debug=ALL
 DebugConfigInfo=ON

More plugins can be added based on your requirements, the plugin list can be found here

http://docs.oracle.com/cd/E15051_01/wls/docs103/plugins/plugin_params.html

Now the sample output from  C:Inetpubwwwroot directory looks like below.

sample_out

And in IIS6.0 it looks like below.

iis_basic

I’m using Default website in this example.

Steps

  1. Start IIS, go to ‘Default Web Site”, right click on it and select ‘properties’,                         go to ‘ISAPI Filters’ tab, click on Add
  2. Default-prop

isapi-filter

Enter the name of your choice for the “Filter name” eg: forwarddll

Now click on browse and select “iisforward.dll“,  and click on OK, as shown below.

fwd-dll

Go to the Home Directory, select configuration and select add

add_wlforward

Select browse, then iisproxy.dll from drop down list and for extension use .wlforward

and make sure “Verify that the file exits” is not checked (See last check box on screen above and screen shot below point 6).

Then click OK.

Next go to Web Service Extension and make sure that “All Unknown ISAPI Extensions” are allowed.

WebserviceExt

Here completes the configuration.

Now  you can access you weblogic url via, WLS iis proxy.

for example, in original your application is configured on weblogic port 7001

like:
http://myhost.wlmachine.com:7001/sampleapp
This can be accessed as
http://myhost.wlmachine.com/sampleapp

ORA-00845: MEMORY_TARGET not supported on this system

Getting ORA-00845: MEMORY_TARGET not supported on this system, while trying to start a database.

Error
sql> startup
ORA-00845: MEMORY_TARGET not supported on this system

Reason:

This is a very common error which you might face while starting up your oracle database. This happens when your system is out of temporary storage. While starting up the database oracle uses /dev/shm to store temporary files but when it runs out of memory you get this error.

/dev/shm is also know as tmpfs i.e. temporary file system which keeps all the file system in virtual memory to speed up several processes.

Solution:

Increase the size of /dev/shm

To check the size of /dev/shm
root@localhost# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda3 10G 4.4G 2.9G 61% /
tmpfs 504M 76K 504M 1% /dev/shm
/dev/sda1 194M 25M 160M 14% /boot

To increase the size
root@localhost# mount -o remount,size=3G /dev/shm
Verify the size
root@localhost# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda3 7.6G 4.4G 2.9G 61% /
tmpfs 3G 1007M 2.1G 33% /dev/shm
/dev/sda1 194M 25M 160M 14% /boot

To make permanent changes to your file system update your fstab
root@localhost# vi /etc/fstab
tmpfs /dev/shm tmpfs defaults,size=3G 0 0

 

Update the new fstab file
root@localhost# mount -a
 

ORA-01034: ORACLE Not Available

What to do when we get  errors  like ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist.

Solution:

The ORA-01034 is  simple error, it means that your database is down!  Oracle oerr utility notes this about the ORA-01034 error:

ORA-01034: ORACLE not available

Cause:

 Oracle was not started up. Possible causes include the following:

  • The SGA requires more space than was allocated for it.
  • The operating-system variable pointing to the instance is improperly defined.

Action: 

Refer to accompanying messages for possible causes and correct the problem mentioned in the other messages. If Oracle has been initialized, then on some operating systems, verify that Oracle was linked correctly. See the platform specific Oracle documentation.

You may find that you are experiencing ORA-01034 when attempting to upgrade your Oracle database.ORA-01034 is thrown during the attempt to upgrade because there is an invalid entry in one of the following files:

  1. /etc/oratab
  2. /var/opt/oracle/oratab

The ORA-01034 is a result of a discrepancy between ORACLE_HOME andORACLE_SID

To resolve ORA-01034, be sure that the ORACLE_HOME and ORACLE_SIDproperly match within the files /etc/oratab or /var/opt/oracle/oratab .

 

© 2017 My techbook

Theme by Anders NorénUp ↑