Total Pageviews

Sunday, April 1, 2018

oracle database tablespace size information





SELECT a.file_name,
       substr(A.tablespace_name,1,14) tablespace_name,
       trunc(decode(A.autoextensible,'YES',A.MAXSIZE-A.bytes+b.free,'NO',b.free)/1024/1024) free_mb,
       trunc(a.bytes/1024/1024) allocated_mb,
       trunc(A.MAXSIZE/1024/1024) capacity,
       a.autoextensible ae
FROM (
     SELECT file_id, file_name,
            tablespace_name,
            autoextensible,
            bytes,
            decode(autoextensible,'YES',maxbytes,bytes) maxsize
     FROM   dba_data_files
     GROUP BY file_id, file_name,
              tablespace_name,
              autoextensible,
              bytes,
              decode(autoextensible,'YES',maxbytes,bytes)
     ) a,
     (SELECT file_id,
             tablespace_name,
             sum(bytes) free
      FROM   dba_free_space
      GROUP BY file_id,
               tablespace_name
      ) b
WHERE a.file_id=b.file_id(+)
AND A.tablespace_name=b.tablespace_name(+)
ORDER BY A.tablespace_name ASC;

installing Weblogic at windows 2012 server


  • Run the Oracle WebLogic 10.3.6.0 installer from the image that you downloaded from the Oracle Software Delivery Cloud.
    The item name of the installer is (V29856-01). The filename of the installer is:
    wls1036_generic.jar
    Upon execution, the installer starts preparing the OUI install program.
  • Open a Command window with Run as Administrator option and run this command from the prompt:
    >java -jar wls1036_generic.jar

  • On Choose Middleware Home Directory, click this radio button:
    Create a new Middleware Home
    For example, your Middleware Home Directory might be:

    C:\Oracle\Middleware

  • On Register for Security Updates, Oracle strongly recommends you complete the Email address and/or the My Oracle Support Password fields to register your installation of Oracle WebLogic 10.3.6.0. This registration will enable you to be informed of security issues.
  • Click the Next button

  • On Choose Install Type, select the type of installation you wish to perform.
    In this guide, it is assumed you select the Typical installation type, which installs the Oracle WebLogic 10.3.6.0 and the Oracle Coherence Server.

  •  The Typical selection automatically includes the Oracle Coherence server, which is part of Oracle WebLogic 10.3.6.0. This new server is a stand-alone cache server that enables dedicated JVM instances responsible for maintaining and managing cached data. As of the initial publication of this guide, the JD Edwards EnterpriseOne HTML Server has not been certified with the Oracle Coherence Server.

  • On JDK Selection, click the check box for the JDK you wish to use and install with this product installation.
  • Click the Next button.
  • On Choose Product Installation Directories, complete these fields:
    • WebLogic Server
      Enter or browse to a location where you wish to install an Oracle WebLogic 10.3.6.0.
      For example:
      c:\Oracle\Middleware\wlserver_10.3
    • Oracle Coherence
      Enter or browse to a location where you wish to install the Oracle Coherence Server.
      For example:
      c:\Oracle\Middleware\coherence_3.7
  • Click the Next button.

  • If the above screen does display (because you are not running the installer as an Administrator), on Choose Shortcut Location, click this radio button:
    "All Users" Start Menu folder (recommended)
  • Click the Next button.

  • On Installation Summary, review the products that will be installed.
  • Click the Next button.


  • The installer starts copying files.
    A progress bar is displayed in the lower right-hand portion of the screen.
    As the installer progresses it displays the new features of the Oracle WebLogic 10.3.6.0.
  • nmConnect() error WLSTException: Error occured while performing nmConnect : Cannot connect to Node



    Connecting to Node Manager ...
    Traceback (innermost last):
      File "<console>", line 1, in ?
      File "<iostream>", line 123, in nmConnect
      File "<iostream>", line 648, in raiseWLSTException
    WLSTException: Error occured while performing nmConnect : Cannot connect to Node
    Manager. : Access to domain 'my_domain' for user 'weblogic' denied
    Use dumpStack() to view the full stacktrace


    Solution:
    if it is new installation update Weblogic credential information.



    Cannot open TEMP post file /tmp/_wl_proxy/_

    From oracle

    Location of POST Data Files

    When the FileCaching parameter is set to ON, and the size of the POST data in a request is greater than 2048 bytes, the POST data is first read into a temporary file on disk and then forwarded to the WebLogic Server in chunks of 8192 bytes. This preserves the POST data during failover.
    The temporary POST file is located under /tmp/_wl_proxy for UNIX. For Windows it is located as follows (if WLTempDir is not specified):
    1. Environment variable TMP
    2. Environment variable TEMP
    3. C:\Temp
    /tmp/_wl_proxy is a fixed directory and is owned by the HTTP Server user. When there are multiple HTTP Servers installed by different users, some HTTP Servers might not be able to write to this directory. This condition results in an error.
    To correct this condition, use the WLTempDir parameter to specify a different location for the _wl_proxy directory for POST data files.

     here is what i use to fix it

    I have created folder under /tmp/_wl_proxy and it resolved the error.

    to check nodemanager error from running logs


    nodemanager error

    ps -ef | grep -v grep | grep -i weblogic.NodeManager

    startup error



    DeploymentService> <BEA-290074> <Deployment service servlet received file download request for file "config/jdbc/security/SerializedSystemIni.dat". The file may exist, but download of this file is not allowed

    Solution:

    -Dweblogic.data.canTransferAnyFile=true

    Wednesday, March 28, 2018

    what is RelayState what it meant for during SAML SP request







     Along with a SAML Request, an HTTP parameter called RelayState is passed along to the Identity Provider SSO Access Manager. This captures the location of the resource the user originally requested. In simple it is Endpoint where user want to go after the Successful Authentication.


    Endpoint https://sp.mysite.com:9031/sp/ACS.saml2