11.5.10 INSTANCE에서 FRD LOG 생성하는 방법

제품: AOL
작성날짜 : 2006-05-11
11.5.10 INSTANCE에서 FRD LOG 생성하는 방법
==========================================
PURPOSE
11.5.10 UI Forms에서 발생하는 issue 해결 도움을 위해 Support 및
Development가 이용하는 FRD Trace log 생성하는 방법을 알아본다.
Explanation
11.5.10 instance에서 FRD를 생성하기 위해 아래 steps을 따른다.
1.Apps user로 Unix session instance에 login 한다.
모든 환경 변수를 display 하기 위해 set command 이용한다.
Find the variable “FORMS60_TRACE_PATH”
이 directory path는 FRD file 생성에 이용되며,아래 설명되는 ICX Profile
URL의 한 부분이다.
2.Application의 System Administrator responsibility에 login 한다.
3.아래 profile을 User Level에 추가,본인의 "host.domain.country”과
"FORMS60_TRACE_PATH"은 제외한다.
ICX: Forms Launcher = http://host.domain.com:8000/dev60cgi/f60cgi?
&record=collect&log=/forms60_trace_path/Your_Name.FRD.log
본인의 host.domain.com을 위에 대신 넣고,“&log=”directory section 엔
당신의 FORMS60_TRACE_PATH를 입력한다.
개인의 capture를 위해 USERNAME.FRD.log를 이용한다.
11.5.10 에서는 Security 이유로 logging directory가 usr_dump_dest에서
FORMS60_TRACE_PATH 환경 변수로 변경되었다.
"&record" 시작 부분에 "?play="가 없어졌으며,"f60cgi?"에 "/"도 없다.
Directory에 접근하거나 login을 위해 Putty나 다른 ftp connection
software를 이용해야만 하고,FRD file을 unix directory에서 개인 PC로
ftp할 필요가 있다.
4.Application을 lotout, OM super user로 다시 login 한다.
5.Login 하면 'Logging FRD' message를 볼 수 있을 것이다.
6.FRD log 생성을 위해 필요한 forms navigations을 실행한다.
7.FRD logging이 끝나면 FRD file을 close 하기 위해 application을
logout 하고, local PC에 생성된 FRD를 ftp 한다.
8.FRD 생성후에는 performance 문제가 있으므로 본인의 이름으로 setting
한 profile "ICX: Forms Launcher" 값을 remove 한다.
이 profile이 있으면 매번 login시마다 FRD가 실행되게 된다.
Reference Documents
Note 335872.1

제품: AOL
작성날짜 : 2006-05-11
11.5.10 INSTANCE에서 FRD LOG 생성하는 방법
==========================================
PURPOSE
11.5.10 UI Forms에서 발생하는 issue 해결 도움을 위해 Support 및
Development가 이용하는 FRD Trace log 생성하는 방법을 알아본다.
Explanation
11.5.10 instance에서 FRD를 생성하기 위해 아래 steps을 따른다.
1.Apps user로 Unix session instance에 login 한다.
모든 환경 변수를 display 하기 위해 set command 이용한다.
Find the variable “FORMS60_TRACE_PATH”
이 directory path는 FRD file 생성에 이용되며,아래 설명되는 ICX Profile
URL의 한 부분이다.
2.Application의 System Administrator responsibility에 login 한다.
3.아래 profile을 User Level에 추가,본인의 "host.domain.country”과
"FORMS60_TRACE_PATH"은 제외한다.
ICX: Forms Launcher = http://host.domain.com:8000/dev60cgi/f60cgi?
&record=collect&log=/forms60_trace_path/Your_Name.FRD.log
본인의 host.domain.com을 위에 대신 넣고,“&log=”directory section 엔
당신의 FORMS60_TRACE_PATH를 입력한다.
개인의 capture를 위해 USERNAME.FRD.log를 이용한다.
11.5.10 에서는 Security 이유로 logging directory가 usr_dump_dest에서
FORMS60_TRACE_PATH 환경 변수로 변경되었다.
"&record" 시작 부분에 "?play="가 없어졌으며,"f60cgi?"에 "/"도 없다.
Directory에 접근하거나 login을 위해 Putty나 다른 ftp connection
software를 이용해야만 하고,FRD file을 unix directory에서 개인 PC로
ftp할 필요가 있다.
4.Application을 lotout, OM super user로 다시 login 한다.
5.Login 하면 'Logging FRD' message를 볼 수 있을 것이다.
6.FRD log 생성을 위해 필요한 forms navigations을 실행한다.
7.FRD logging이 끝나면 FRD file을 close 하기 위해 application을
logout 하고, local PC에 생성된 FRD를 ftp 한다.
8.FRD 생성후에는 performance 문제가 있으므로 본인의 이름으로 setting
한 profile "ICX: Forms Launcher" 값을 remove 한다.
이 profile이 있으면 매번 login시마다 FRD가 실행되게 된다.
Reference Documents
Note 335872.1

Similar Messages

  • ERP FORMS TRACE(FRD) LOG FILE 만드는 방법 - R11.5.X

    제품 : AOL
    작성날짜 : 2005-04-27
    ERP FORMS TRACE(FRD) LOG FILE 만드는 방법 - R11.5.X
    ==============================================
    PURPOSE
    ERP Forms trace(FRD) log file 만드는 방법 - R11.5.X
    Explanation
    FORM level에서의 Error를 추적하기 위한 방법으로
    FRD log 라는 것이 있습니다.
    해당 log file은 FORM level의 Data입출력을 보여주는 것입니다.
    여기서는 R11.5.X version대에서의 log file만드는 방법에 대해서
    설명하겠습니다.
    1. ERP US(영문) Version일 경우
    http://serverhostname:port/dev60cgi/f60cgi?&config=DBSID&record=collect&log=쓰기가 가능한 Directory/form_trc.txt&lang=US
    처음 ERP접속시 위와 같이 argument를 입력하시면, form_trc.txt file안에 다 기록됩니다.
    그렇기 때문에, file size를 줄이기 위해 가급적 문제 재현까지 바로 이동해주시고, Server상에서 해당 Form trace file을 tail -f 로 확인하시다가 문제현상이 발생하는 시점까지 도달하셨으면, ERP화면에서는 더이상 작업을 하지 말아주시고, Server상의 form_trc.txt file을 확인할 수 있습니다.
    실제 Parameter가 적용된 예제는 아래와 같습니다.
    고객님의 환경에 맞게 Server Host name및 Port등을 변경하셔서 ERP접속시 정확히 입력해주시기 바랍니다.
    예)
    http://ERP.oracle.co.kr:8000/dev60cgi/f60cgi?&config=PROD&record=collect&log=/u01/app/oraERP/temp/form_trc.txt&lang=US
    ===================================================================================================
    2. ERP NLS(한글) Version일 경우
    => 한글 환경에서만 FORM error가 발생하여, 한글 Mode에서 FRD log file을 생성해야하는 경우에
    사용할 수 있는 방법입니다.
    http://{hostname:port}/dev60cgi/f60cgi?config=PROD&record=collect&log=/u01/app/oraERP/temp/form_trc.txt&lang=KO&env=NLS_LANG='korean_korea.{characterset}'
    (characterset은 현재 설정된 것을 확인해주시고 입력해주시기 바랍니다.)
    예를들어, characterset이 KOREAN_KOREA.KO16KSC5601이라면 아래와 같을 수 있겠습니다.
    http://ERP.oracle.co.kr:8000/dev60cgi/f60cgi?&config=PROD&record=collect&log=/u01/app/oraERP/temp/form_trc.txt&lang=KO&env=NLS_LANG='KOREAN_KOREA.KO16KSC5601'
    다른 방법은 US와 동일하고, Parameter중 "lang"과 "env" parameter를 주의해서 입력하면 됩니다.

    Hi Hamish,
    If you managed to solve this issue, please indicate how, because I'm facing exactly the same...
    Thanks&Regards,
    Philippe

  • How to check instance alert.log in RAC 10g ASM environment?

    i know to use Grid control or OEM check instance alert.log?
    But since in ASM the alert.log is not recognized, how to check it in OS level just like regular non-RAC checking?
    or the best way to check it ?
    thanks a lot!

    user620464 wrote:
    i know to use Grid control or OEM check instance alert.log?
    But since in ASM the alert.log is not recognized, how to check it in OS level just like regular non-RAC checking?
    or the best way to check it ?
    thanks a lot!Well if you mean that you have put the alert over asm storage than where did it mention to put alert file over ASM? Is not like an o/s where one can go and read the file and surely, neither we need striping or mirroring of it either. I am not sure that there is any way to do so over ASM storage.
    HTH
    Aman....

  • ERP FORMS TRACE(FRD) LOG FILE 만드는 방법 - R11.0.X

    제품 : AOL
    작성날짜 : 2005-04-27
    ERP FORMS TRACE(FRD) LOG FILE 만드는 방법 - R11.0.X
    ==============================================
    PURPOSE
    ERP Forms trace(FRD) log file 만드는 방법 - R11.0.X
    Explanation
    FORM level에서의 Error를 추적하기 위한 방법으로
    FRD log 라는 것이 있습니다.
    해당 log file은 FORM level의 Data입출력을 보여주는 것입니다.
    여기서는 R11.0.X version대에서의 log file만드는 방법에 대해서
    설명하겠습니다.
    1.
    ERP system을 접속하실때, http://hostname:port/OA_HTML/US/prod_j.htm 으로 하실 것입니다.
    prod_j.htm file은 Server상에 접속하신 후, $OA_HTML/US directory안에 있습니다.
    2.
    그 prod_j.htm file을 복사본을 먼저 만드시고, vi로 prod_j.htm file을 open후에 그 file의 내용중
    <"module=/.../fnd/11.0.28/forms/US/FNDSCSGN userid=applsyspub/pub@PROD fndnam=apps">
    인 곳이 한곳 나타날 것입니다.
    3.
    FNDSCSGN 뒤의 parameter에 record=collect log=/tmp/oracle_frd.log 를 추가하시면 됩니다.
    즉, 아래와 같이 하시면 됩니다.
    <"module=/.../fnd/11.0.28/forms/US/FNDSCSGN record=collect log=/tmp/oracle_frd.log userid=applsyspub/pub@PROD fndnam=apps">
    추가후에 저장하시고, vi를 빠져나와 주시기 바랍니다.
    4. 주의하실 점은 해당 parameter추가후에는 신규접속하는 모든 기록이 oracle_frd.log file에 기록되게 되어, 저희가 보고자 하는 Error내용이 없어질 수 있습니다.
    가급적 사용하시는 분들이 전혀 없는 시점에 잠깐 수정을 하셨다가 Error를 재현해주시고, 다시 option을 빼주시면 됩니다. 이점 꼭 확인해주시기 바랍니다.
    5. 또한, Error화면까지 최소한의 작업으로 이동해주시면, log file size가 많이 줄어서 분석하는데 시간이 절약됩니다.
    6. log라는 parameter에 기록할 Directory는 temp 말고 Concurrent log file이 생성되는 directory로 해주시면 됩니다.
    만약, 2 node 이상으로 Server를 운용하고 계시다면, APPS server쪽 기록가능한 Directory면 되겠습니다.
    7. Error작업후, Concurrent log가 생성되는 위치로 가주시고, oracle_frd.log file 확인할 수 있습니다.
    Reference Documents
    Note : 148982.1

    HI Niklas,
    Could you please share the value of environment variables from the upgrade dir path (/usr/sap/SID/SUM/abap/exe ).
    Also please follow SAP Note  1966797 - Errors: connect failed due to DbSL load lib failure
    1817743 - ERROR: No connect due to DbSl Load Lib Failure - With tp version 380.03.89
    If possible try to use 721_EXT with SSFS database connection methods.
    Regards,
    Gaurav

  • Instance size logging / monitoring

    I am trying to debug an instance size issue and would like to log/monitor the instance size during process execution.
    I wanted to simply logMessage it and monitor it in Studio but cannot find an appropriate API in the Fuego Catalog, something like...
    logMessage("current instance size = " + Fuego.Papi.Instance.size); Or something similar.
    But no such size attribute exists.
    Any recommendations as to the best way to achieve this logging/monitoring?
    Thanks.

    Hi Michael,
    There's an engine setting (both on Studio and Enterprise) for the maximum allowable size of instance variables.
    You have a few choices:
    1. you can bump the max instance size setting on Studio and Enterprise (not a fan of this)
    2. you can change the offending instance variable(s) to be "Separated" or
    3. you can look at your variable and see if it contains information rarely accessed and possibly should be retrieved from a database.
    good to hear from you,
    Dan

  • How do I make the instance archive logs into additional recovery directory?

    A third party tool reads all the archived logs. After they are processed,the tool can delete them. I want to keep a copy of archived logs.
    Thanks
    Hunter

    Hi..
    Specify the location in one of the log_archive_dest_n (n are numbers ranging from 1 to 10) and for that value of n enable the log_archive_dest_state_n.
    Also, can you post the database version and output of
    sql> show parameter log_archive
    For reference [http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/archredo.htm#ADMIN00801]
    HTH
    Anand
    Edited by: Anand... on Jan 7, 2009 1:13 AM

  • Can one instance have multiple redo threads ?

    i was reading the Oracle Data guard 10g guide and it says
    Determine the appropriate number of standby redo log file groups.
    Minimally, the configuration should have one more standby redo log file group than the number of online redo log file groups on the primary database. However, the recommended number of standby redo log file groups is dependent on the number of threads on the primary database. Use the following equation to determine an appropriate number of standby redo log file groups:
    (maximum number of logfiles for each thread + 1) * maximum number of threads
    Using this equation reduces the likelihood that the primary instance's log writer (LGWR) process will be blocked because a standby redo log file cannot be allocated on the standby database. For example, if the primary database has 2 log files for each thread and 2 threads, then 6 standby redo log file groups are needed on the standby database
    while Oracle's definition of redo log states the following
    Redo Threads
    When speaking in the context of multiple database instances, the redo log for each database instance is also referred to as a redo thread. In typical configurations, only one database instance accesses an Oracle Database, so only one thread is present. In an Oracle Real Application Clusters environment, however, two or more instances concurrently access a single database and each instance has its own thread of redo.
    this is confusing, in a typical environment where only one instance accesses a database, can we have more than one redo thread ?

    Though you can create multiple threads but of no use in NON-RAC or non-parallel server configuration.
    Following is the generic formula. You should consider
    maximum number of threads = 1 for single instance (NON-RAC).
    (maximum number of logfiles for each thread + 1) * maximum number of threads
    Message was edited by:
    Reega

  • What's the meaning of a yellow DB-Adapter service in an ESB Instance?

    Hi Forum,
    I have implemented a really small ESB routing application, taking 3 Values, which will be written to a database using a routing service and a DB-Adapter. When calling this service via URI of the local endpoint (at the definition tab of ESB Control) everything works fine so far.
    Next I tried to invoke this service from a BPEL process. But all I got was a yellow marked DB-Adapter in the ESB instance. This is accompanied by a R tag on the adapter. The details tab states that a rollback has been done because of an error "undefined" on a non transactional endpoint.
    By the way, there is no error tab displayed in ESB Control and moreover no BPEL instance is logged. I asume that is a result of the rollback. So there is pretty few information on what has happened.
    Unfortunately I couldn't find anything of value on the web dealing with non transactional endpoints.
    Has anyone got a clue, what the reason for this strange behavior could be?
    TIA,
    Marco

    Hi James,
    thanks a lot for your answer. You've been totally right, it was a error in payload. Actually, after fiddling about with no success to get it right, I ended up with no ESB instance trace at all :-(
    So I decided to restart the server and guess what, everything looked nice. The instance came up with tracking information and error log showing that the payload was incomplete.
    And even the main problem of being unable to deploy a BPEL-Process because of an undefined partner link type (which I couldn't follow as the PLT was enclosed in the wsdl of the ESB service and that led me to designing a small repro case) vanished into thin air.
    This SOA-Suite seems to be a sort of weird. At the moment I can't figure out how to successfully run a real-life project using this technology :-(
    Working on a research project now, I hope to be getting more experienced before it gets down to business.
    Cheers
    Marco

  • Question about using EM on machine with 2 active instances

    Good morning,
    As a self training exercise I've created 2 instances on one machine. The machine is both, server and client. I'm running Windows XP SP2, Oracle 11gR2 (as seen in my user handle) and using IE7 for EM.
    The URL for the first instance is:
    https://Oracle2Day1.john.local:1158/emThe URL for the second instance is:
    https://Oracle2Day1.john.local:5500/emIf I log into one and only one instance then everything works just fine.
    When I log into the first instance, then log into the second instance and, switch back to the tab of the first instance, I find myself back at the "User name/Password/Connect As" page, I don't even get the page saying that I've been logged out of the first instance.
    Additionally, if at that point, I switch back to the tab of the second instance, I find myself at the "User name/Password/Connect As" page for that instance too.
    Basically, whenever I log into both instances and switch from one instance tab to the other, it brings me back to the log in page for both instances.
    If I log into a single instance and do not attempt to log into the second instance then everything works fine.
    Any ideas as to why I cannot be logged into both instances at the same time ? (I can be logged in both instances simultaneously using SQL*Plus without any problems) Is there something I can do to correct this behavior or is this "normal" ?
    Thank you for your help,
    John.

    Hello Amardeep,
    >
    If he opens the 2 EM consoles in 2 separate browsers, shouldn't it work ?
    >
    I tried that. I even tried different browsers and had all kinds of problems. Nothing worked but, in order to tell you about the problems I would run into when doing that, I tried it again using IE7 and, this time, I made sure I had a separate process for each copy of IE7 (not just a separate thread)....
    LOW and BEHOLD... it worked!!!
    I can do whatever I want in both instances without any problems... smooth as silk.
    I spent a day and half trying to figure out what the problem was. The strange thing was that when I had just finished installing the second instance, everything worked fine. I could be in both instances at the same time. After I rebooted the machine, it would no longer work... so I started looking everywhere for the reason why it broke... I'm guessing that when I rebooted my machine, (which is not particularly fast and, less so when there are two instances running), I tried too soon (it takes my machine over 30 minutes just to initialize both instances) and that contributed to all of the problems I experienced. I probably did not try two separate browser processes before each instance had time to fully initialize.
    Problem solved.
    Solution:
    *1*. Make sure the instance is fully initialized (wait until CPU drops to 1 to 4% and stays there for a few minutes)
    *2*. Access each instance using a different browser process (make sure the browser window isn't simply another thread of a previously started browser instance)
    Amardeep, thank you :)
    John.

  • Multiple materialized views against same mv logs

    Hi,
    I am currently moving an apex installation that uses materialized views for data source from one machine to another (both 11.1.0.6, diff nls_character sets WE8MSWIN1252 to AL32UTF8, so dpexp/dpimp is not working due to bug).
    I am looking at exp/imp apex workspaces/apps and building the same mviews in the new instance clean and refreshing.
    1.) I want to know if building and refreshing the new mviews copies ahead of cutover will have any impact on the curr prod instances mview logs (there are two) and or the curr apex install that is also refreshing from the same logs.
    I want to make sure buliding and refreshing the new mview copies won't effect/corrupt anything currently being use in the current setup, the documentation I've found so far is very vague so if anyone has found any ML notes or other links that would be awesome too.
    Thanks, Chris

    To clarify what you are saying:
    Database A - Master_Table with mview_log
    Database B - Fast Refresh mview pointing @ database A and master_table
    Database C - Fast Refresh mview pointing @ database A and master_table
    I've done this @ 10.2.0.4 and it worked OK without causing any issues to the existing configuration so unless 11.1.0.6 introduced a new bug you should be OK.
    HTH
    Paul

  • Terminating the instance due to error 119

    System : Oracle 11gR2 running on Oracle VM.
    Issue : Oracle fails to comeup after LISTENER.ORA is removed/corrupted. Any reason?
    Actions taken : used *.ora files from backup taken during healthy state and dbstart works fine now.
    Resolved but Question : Does dbstart depend on *.ora files availability? What is this error 119 (couldnt find any info on that)?
    Thanks.

    Dear sb92075,
    Thanks for confirming :
    listener is NOT required to start or access any local Oracle database.
    listener.ora file is NOT required to start or use the listener.
    Coming to ...
    It is really, Really, REALLY difficult to fix a problem that can not be seen.
    As said earlier, issue is fixed.  Question is why DBSTART works only when proper ORA files are used.
    Anyways, here is the info requested :
    [oracle@oraclelinux6 bin]$ dbstart
    ORACLE_HOME_LISTNER is not SET, unable to auto-start Oracle Net Listener
    Usage: /apps/app/oracle/product/11.2.0/dbhome_1/bin/dbstart ORACLE_HOME
    Processing Database instance "orcl": log file /apps/app/oracle/product/11.2.0/dbhome_1/startup.log
    [oracle@oraclelinux6 bin]$
    From startup log :
    SQL*Plus: Release 11.2.0.1.0 Production on Mon Dec 2 18:47:47 2013
    Copyright (c) 1982, 2009, Oracle.  All rights reserved.
    SQL> Connected to an idle instance.
    SQL> ORA-00119: invalid specification for system parameter LOCAL_LISTENER
    ORA-00132: syntax error or unresolved network name 'LISTENER_ORCL'
    SQL> Disconnected
    /apps/app/oracle/product/11.2.0/dbhome_1/bin/dbstart: Database instance "orcl" warm started.
    [oracle@oraclelinux6 bin]$
    From trace file :
    *** 2013-12-02 18:47:58.236
    USER (ospid: 3950): terminating the instance due to error 119
    [oracle@oraclelinux6 trace]$
    From alert log :
    Starting up:
    Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options.
    Using parameter settings in server-side spfile /apps/app/oracle/product/11.2.0/dbhome_1/dbs/spfileorcl.ora
    System parameters with non-default values:
      processes                = 150
      memory_target            = 1584M
      control_files            = "/apps/db/orcl/control01.ctl"
      control_files            = "/apps/app/oracle/flash_recovery_area/orcl/control02.ctl"
      db_block_size            = 8192
      compatible               = "11.2.0.0.0"
      db_recovery_file_dest    = "/apps/app/oracle/flash_recovery_area"
      db_recovery_file_dest_size= 3882M
      undo_tablespace          = "UNDOTBS1"
      remote_login_passwordfile= "EXCLUSIVE"
      db_domain                = "localdomain"
      dispatchers              = "(PROTOCOL=TCP) (SERVICE=orclXDB)"
      local_listener           = "LISTENER_ORCL"
      audit_file_dest          = "/apps/app/oracle/admin/orcl/adump"
      audit_trail              = "DB"
      db_name                  = "orcl"
      open_cursors             = 300
      diagnostic_dest          = "/apps/app/oracle"
    USER (ospid: 2999): terminating the instance due to error 119
    Instance terminated by USER, pid = 2999
    Mon Dec 02 18:47:51 2013
    Starting ORACLE instance (normal)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Picked latch-free SCN scheme 3
    Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST
    Autotune of undo retention is turned on.
    IMODE=BR
    ILAT =27
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    Starting up:
    Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options.
    Using parameter settings in server-side spfile /apps/app/oracle/product/11.2.0/dbhome_1/dbs/spfileorcl.ora
    System parameters with non-default values:
      processes                = 150
      memory_target            = 1584M
      control_files            = "/apps/db/orcl/control01.ctl"
      control_files            = "/apps/app/oracle/flash_recovery_area/orcl/control02.ctl"
      db_block_size            = 8192
      compatible               = "11.2.0.0.0"
      db_recovery_file_dest    = "/apps/app/oracle/flash_recovery_area"
      db_recovery_file_dest_size= 3882M
      undo_tablespace          = "UNDOTBS1"
      remote_login_passwordfile= "EXCLUSIVE"
      db_domain                = "localdomain"
      dispatchers              = "(PROTOCOL=TCP) (SERVICE=orclXDB)"
      local_listener           = "LISTENER_ORCL"
      audit_file_dest          = "/apps/app/oracle/admin/orcl/adump"
      audit_trail              = "DB"
      db_name                  = "orcl"
      open_cursors             = 300
      diagnostic_dest          = "/apps/app/oracle"
    USER (ospid: 3950): terminating the instance due to error 119
    Instance terminated by USER, pid = 3950
    [oracle@oraclelinux6 trace]$
    [oracle@oraclelinux6 trace]$ df -k
    Filesystem                          1K-blocks      Used Available Use% Mounted on
    /dev/mapper/vg_oraclelinux6-lv_root  15237120   8088772   5709648  59% /
    tmpfs                                 5242880       272   5242608   1% /dev/shm
    /dev/sda1                              495844    125202    345042  27% /boot
    /dev/sdd                             12385456  10527572   1228740  90% /apps
    none                                  4194304       108   4194196   1% /tmp
    Linux                               353894396 300370788  53523608  85% /media/sf_Linux
    /dev/sr0                                54082     54082         0 100% /media/VBOXADDITIONS_4.2.4_81684
    [oracle@oraclelinux6 trace]$ ps -ef | grep oracle
    avahi     1513     1  0 18:43 ?        00:00:00 avahi-daemon: running [oraclelinux6.local]
    oracle    2354     1  0 18:45 ?        00:00:00 /usr/bin/gnome-keyring-daemon --daemonize --login
    oracle    2363  2344  0 18:45 ?        00:00:00 gnome-session
    oracle    2371     1  0 18:45 ?        00:00:00 dbus-launch --sh-syntax --exit-with-session
    oracle    2372     1  0 18:45 ?        00:00:00 /bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
    oracle    2435     1  0 18:45 ?        00:00:00 /usr/bin/VBoxClient --clipboard
    oracle    2443     1  0 18:45 ?        00:00:00 /usr/bin/VBoxClient --display
    oracle    2448     1  0 18:45 ?        00:00:00 /usr/bin/VBoxClient --seamless
    oracle    2453     1  0 18:45 ?        00:00:01 /usr/bin/VBoxClient --draganddrop
    oracle    2477     1  0 18:45 ?        00:00:00 /usr/libexec/gconfd-2
    oracle    2484     1  0 18:45 ?        00:00:00 /usr/libexec/gnome-settings-daemon
    oracle    2491     1  0 18:45 ?        00:00:00 /usr/libexec/gvfsd
    oracle    2494     1  0 18:45 ?        00:00:00 seahorse-daemon
    oracle    2502  2363  0 18:45 ?        00:00:00 metacity --sm-client-id 1072b0438d14c83ab2138561248658457800000023660026
    oracle    2506     1  0 18:45 ?        00:00:00 /usr/bin/pulseaudio --start --log-target=syslog
    oracle    2511  2363  0 18:45 ?        00:00:00 gnome-panel --sm-client-id 1072b0438d14c83ab2138561248661659600000023660027
    oracle    2519  2506  0 18:45 ?        00:00:00 /usr/libexec/pulse/gconf-helper
    oracle    2520  2363  0 18:45 ?        00:00:00 nautilus --sm-client-id 1072b0438d14c83ab2138561248673276200000023660028 --sm-client-state-file /home/oracle/.config/session-state/nautilus-1386038529.state
    oracle    2522     1  0 18:45 ?        00:00:00 /usr/libexec/bonobo-activation-server --ac-activate --ior-output-fd=18
    oracle    2528     1  0 18:45 ?        00:00:00 /usr/libexec/wnck-applet --oaf-activate-iid=OAFIID:GNOME_Wncklet_Factory --oaf-ior-fd=18
    oracle    2530     1  0 18:45 ?        00:00:00 /usr/libexec/trashapplet --oaf-activate-iid=OAFIID:GNOME_Panel_TrashApplet_Factory --oaf-ior-fd=24
    oracle    2532     1  0 18:45 ?        00:00:00 /usr/libexec/gvfs-gdu-volume-monitor
    oracle    2538     1  0 18:45 ?        00:00:00 /usr/libexec/gvfsd-trash --spawner :1.7 /org/gtk/gvfs/exec_spaw/0
    oracle    2544  2363  0 18:45 ?        00:00:00 gnome-volume-control-applet
    oracle    2545  2363  0 18:45 ?        00:00:00 /usr/libexec/polkit-gnome-authentication-agent-1
    oracle    2546  2363  0 18:45 ?        00:00:00 gpk-update-icon
    oracle    2551     1  0 18:45 ?        00:00:00 /usr/libexec/gvfs-gphoto2-volume-monitor
    oracle    2605  2363  0 18:45 ?        00:00:00 abrt-applet
    oracle    2606  2363  0 18:45 ?        00:00:00 nm-applet --sm-disable
    oracle    2607  2363  0 18:45 ?        00:00:00 gnome-power-manager
    oracle    2608  2363  0 18:45 ?        00:00:00 bluetooth-applet
    oracle    2611     1  0 18:45 ?        00:00:00 /usr/libexec/gvfs-afc-volume-monitor
    oracle    2612  2363  0 18:45 ?        00:00:00 /usr/libexec/gdu-notification-daemon
    oracle    2614  2363  0 18:45 ?        00:00:00 python /usr/share/system-config-printer/applet.py
    oracle    2625     1  0 18:45 ?        00:00:00 gnome-screensaver
    oracle    2627     1  0 18:45 ?        00:00:00 /usr/libexec/im-settings-daemon
    oracle    2780     1  0 18:45 ?        00:00:00 /usr/libexec/gconf-im-settings-daemon
    oracle    2786     1  0 18:45 ?        00:00:00 /usr/libexec/clock-applet --oaf-activate-iid=OAFIID:GNOME_ClockApplet_Factory --oaf-ior-fd=19
    oracle    2788     1  0 18:45 ?        00:00:00 /usr/libexec/gdm-user-switch-applet --oaf-activate-iid=OAFIID:GNOME_FastUserSwitchApplet_Factory --oaf-ior-fd=28
    oracle    2790     1  0 18:45 ?        00:00:00 /usr/libexec/notification-area-applet --oaf-activate-iid=OAFIID:GNOME_NotificationAreaApplet_Factory --oaf-ior-fd=34
    oracle    2792     1  0 18:45 ?        00:00:00 /usr/bin/gnote --panel-applet --oaf-activate-iid=OAFIID:GnoteApplet_Factory --oaf-ior-fd=40
    oracle    2837     1  0 18:45 ?        00:00:00 /usr/libexec/gvfsd-burn --spawner :1.7 /org/gtk/gvfs/exec_spaw/1
    oracle    2839     1  0 18:45 ?        00:00:00 /usr/libexec/gvfsd-metadata
    oracle    3863     1  0 18:46 ?        00:00:01 gnome-terminal
    oracle    3864  3863  0 18:46 ?        00:00:00 gnome-pty-helper
    oracle    3865  3863  0 18:46 pts/0    00:00:00 bash
    oracle    3881  3863  0 18:46 pts/1    00:00:00 bash
    oracle    3896  3863  0 18:46 pts/2    00:00:00 bash
    oracle    4012  3896  0 18:54 pts/2    00:00:00 ps -ef
    oracle    4013  3896  0 18:54 pts/2    00:00:00 grep oracle
    [oracle@oraclelinux6 trace]$

  • NPE in stopWeblogic.cmd with Server Logging Bridge

    I'm migrating an EAR that depends on JDK logging to WLS 10.3.3. To activate the JDK logging in my domain logs I followed [url http://download.oracle.com/docs/cd/E14571_01/web.1111/e13739/logging_services.htm#WLLOG199]the instructions given in the WLS manual. The logging part works as expected now. However, my stopWeblogic.cmd fails with the following NPE:
    Stopping Weblogic Server...
    Initializing WebLogic Scripting Tool (WLST) ...
    Welcome to WebLogic Server Administration Scripting Shell
    Type help() for help on available commands
    Connecting to t3://DT04748:7001 with userid weblogic ...
    WLST detected that the RuntimeMBeanServer is not enabled. This
    might happen if the RuntimeMBeanServer is disabled via the JMXMBean.
    Please ensure that this MBeanServer is enabled. Online WLST cannot
    function without this MBeanServer.
    This Exception occurred at Thu Jan 06 13:20:24 CET 2011.
    java.lang.NullPointerException
            at weblogic.logging.ServerLoggingHandler.publish(ServerLoggingHandler.java:24)
            at java.util.logging.Logger.log(Logger.java:481)
            at java.util.logging.Logger.doLog(Logger.java:503)
            at java.util.logging.Logger.logp(Logger.java:619)
            at com.sun.jmx.remote.util.ClassLogger.finer(ClassLogger.java:130)
            at com.sun.jmx.remote.util.ClassLogger.trace(ClassLogger.java:88)
            at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:333)
            at weblogic.management.remote.common.WLSRMIConnector.doConnect(WLSRMIConnector.java:150)
            at weblogic.management.remote.common.WLSRMIConnector.access$100(WLSRMIConnector.java:27)
            at weblogic.management.remote.common.WLSRMIConnector$2.run(WLSRMIConnector.java:138)
            at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
            at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
            at weblogic.security.Security.runAs(Security.java:61)
            at weblogic.management.remote.common.WLSRMIConnector.connect(WLSRMIConnector.java:136)
            at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
            at weblogic.management.scripting.WLSTHelper.lookupMBeanServerConnection(WLSTHelper.java:678)
            at weblogic.management.scripting.WLSTHelper.initRuntimeServerConnection(WLSTHelper.java:398)
            at weblogic.management.scripting.WLSTHelper.initConnections(WLSTHelper.java:315)
            at weblogic.management.scripting.WLSTHelper.connect(WLSTHelper.java:203)
            at weblogic.management.scripting.WLScriptContext.connect(WLScriptContext.java:61)
            at weblogic.management.scripting.utils.WLSTUtil.initializeOnlineWLST(WLSTUtil.java:147)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:597)
            at org.python.core.PyReflectedFunction.__call__(Unknown Source)
            at org.python.core.PyMethod.__call__(Unknown Source)
            at org.python.core.PyObject.__call__(Unknown Source)
            at org.python.core.PyObject.invoke(Unknown Source)
            at org.python.pycode._pyx4.connect$1(<iostream>:16)
            at org.python.pycode._pyx4.call_function(<iostream>)
            at org.python.core.PyTableCode.call(Unknown Source)
            at org.python.core.PyTableCode.call(Unknown Source)
            at org.python.core.PyFunction.__call__(Unknown Source)
            at org.python.pycode._pyx15.f$0(D:\Oracle\Middleware\user_projects\domains\FLUX\shutdown.py:6)
            at org.python.pycode._pyx15.call_function(D:\Oracle\Middleware\user_projects\domains\FLUX\shutdown.py)
            at org.python.core.PyTableCode.call(Unknown Source)
            at org.python.core.PyCode.call(Unknown Source)
            at org.python.core.Py.runCode(Unknown Source)
            at org.python.util.PythonInterpreter.execfile(Unknown Source)
            at weblogic.management.scripting.WLST.main(WLST.java:131)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:597)
            at weblogic.WLST.main(WLST.java:29)
    Problem invoking WLST - Traceback (innermost last):
      File "D:\Oracle\Middleware\user_projects\domains\FLUX\shutdown.py", line 6, in ?
      File "<iostream>", line 22, in connect
      File "<iostream>", line 646, in raiseWLSTException
    WLSTException: Error occured while performing connect : "Cannot connect to WLST."
    Use dumpStack() to view the full stacktrace
    Done
    Stopping Derby Server...
    Steps to reproduce
    1. Create a logging.properties file with the following contents:
    # Specify the handlers to create in the root logger
    handlers = weblogic.logging.ServerLoggingHandler
    # Register handlers for my.app and their child loggers
    my.app.handlers = java.util.logging.ConsoleHandler, weblogic.logging.ServerLoggingHandler
    # Do not send the my.app log messages to the root handler
    my.app.useParentHandlers = false
    # Set the default logging level for the root logger
    .level = ALL
    # Set the default logging level for new ConsoleHandler instances
    java.util.logging.ConsoleHandler.level = INFO
    # Set the default logging level for new FileHandler instances
    weblogic.logging.ServerLoggingHandler.level = ALL2. Add the following directive in the setDomainEnv.cmd:
    set JAVA_OPTIONS=%JAVA_OPTIONS% -Djava.util.logging.config.file=path/to/logging.properties3. Start-stop the domain and the above NPE occurs while WLS keeps running. Remove the directive from step 2 and the start-stop sequence goes back to normal.
    Environment
    Oracle JDK:
    java version "1.6.0_23"
    Java(TM) SE Runtime Environment (build 1.6.0_23-b05)
    Java HotSpot(TM) Client VM (build 19.0-b09, mixed mode, sharing)OS: Windows XP Pro SP3
    Your help would be very much appreciated! Please let me know if you need any additional info.
    Thanks,
    Bas

    Hi Sandeep,
    Thanks a lot for your quick reply! You were right, the logging directive was used both client and server side. I moved
    -Djava.util.logging.config.file=path/to/logging.propertiesfrom setDomainEnv.cmd to startWeblogic.cmd and WLS can be stopped correctly now.
    Regards,
    Bas

  • Problem in instance

    User login to sap ...but user can't run any t-codes ...if he run the t-code getting  'error generating screen text'..
    i have checked the system me also getting same error ..and i checked wp in oslevel all r waiting statues and os collector is running ....and restart the system also ...still i am getting error ,while restart it shows like this
    hd306c:dbeadm 71> stopsap
    Stopping the SAP R/3 DBE Processes
    Shutdown-Log is written to /home/dbeadm/stopsap_hd306c_71.log
    Instance DVEBMGS71 was not running!
    Stopping SAP R/3 DBE Database
    Shutdown-Log is written to /home/dbeadm/stopdb.log
    Database stopped
    hd306c:dbeadm 72> startsap
    Starting SAP-Collector Daemon
    05:56:46 13.05.2007 WARNING:  Effective userid not root! Expect problems !
    open logfile '/usr/sap/tmp/dev_coll.tmp' failed... /tmp/
    open logfile '/tmp/dev_coll.tmp' failed... use stderri
    05:56:46 13.05.2007   LOG: ====================================================================================
    05:56:46 13.05.2007   LOG: =                           OS Collector Start
    05:56:46 13.05.2007   LOG: ====================================================================================
    05:56:46 13.05.2007   LOG: Starting /usr/sap/DBE/SYS/exe/run/saposcol
    05:56:46 13.05.2007   LOG: Saposcol Version is [COLL 20.77 02/05/06 46D - AIX v4.08 5L-64 bit 030206]
    This is Saposcol Version COLL 20.77 02/05/06 46D - AIX v4.08 5L-64 bit 030206
    Usage:  saposcol -l: Start OS Collector
            saposcol -k: Stop  OS Collector
            saposcol -d: OS Collector Dialog Mode
            saposcol -s: OS Collector Status
    The OS Collector is already running .....
    saposcol already running
    Checking SAP R/3 DBE Database
    Database is not available via /usr/sap/DBE/SYS/exe/run/R3trans -d -w
    rm: 0653-609 Cannot remove /tmp/o.
    Operation not permitted.
    Could not remove directory /tmp/o
    Remove this directory manually and restart again
    Starting SAP R/3 DBE Database
    Startup-Log is written to /home/dbeadm/startdb.log
    Database started
    Checking SAP R/3 DBE Database
    Database is running
    Starting SAP R/3 Instance
    Startup-Log is written to /home/dbeadm/startsap_hd306c_71.log
    Startup of Instance failed
    See /home/dbeadm/startsap_hd306c_71.log for details
    [1] 1425650
    [1] 1880152
    please hlep asap , for better solution reward.

    Hi Imran
    I see few problems here:
    1.WARNING: Effective userid not root! Expect problems !
    Check if all the permissions are there with the user (sidadm) ,i mean executable permissions.
    2.Your DB is running but ur sap instance is not able to connect to DB and thats why the startup fails.
    3.Database is not available via /usr/sap/DBE/SYS/exe/run/R3trans -d -w
    rm: 0653-609 Cannot remove /tmp/o.
    Operation not permitted.
    Could not remove directory /tmp/o
    Remove this directory manually and restart again
    Have you tried the above instructions.If not do it.I hope ur issue will get solved.
    Reward with suitable points

  • How to get the ACCOUNTING_FLEXFIELD Name  in a Multi Ledger Instance?

    Hi,
    How to get the <ACCOUNTING_FLEXFIELD> Name in a Multi Ledger Instance from logged-in Responsibility? Is there any profile option available?
    SELECT id_flex_num
    INTO l_structure_num
    FROM apps.fnd_id_flex_structures
    WHERE ID_FLEX_CODE = 'GL#'
    AND ID_FLEX_STRUCTURE_CODE=<ACCOUNTING_FLEXFIELD>;
    Tx

    SMOD->SEUED001->Display componens->double click on EXIT_SAPLEDITOR_002->See the source code...
    function exit_sapleditor_002.
    *"*"Lokale Schnittstelle:
    *"       IMPORTING
    *"             VALUE(PROGRAM) LIKE  SY-REPID
    *"       EXCEPTIONS
    *"              CANCELLED
    include zxseuu22 .
    endfunction.
    PROGRAM is the importing parameter for the function module.
    matt

  • How to create an asm instance manaually? oracle 11gr2.

    env: oracle 11gr2 os: hpux or aix single machine , not rac.
    question:how to create an asm instance manaually?? diskgroup,listener,db ,they can be resigistered to crs??
    can anyone give me document about it?

    Hi,
    This is a simple answer:
    Automatic Storage Management (ASM)
    ASM was a new storage option introduced with Oracle Database 10gR1 that provides the services of a filesystem, logical volume manager, and software RAID in a platform-independent manner. ASM can stripe and mirror your disks, allow disks to be added or removed while the database is under load, and automatically balance I/O to remove "hot spots." It also supports direct and asynchronous I/O and implements the Oracle Data Manager API (simplified I/O system call interface) introduced in Oracle9i.
    ASM is not a general-purpose filesystem and can be used only for Oracle data files, redo logs, and control files. Files in ASM can be created and named automatically by the database (by use of the Oracle Managed Files feature) or manually by the DBA. Because the files stored in ASM are not accessible to the operating system, the only way to perform backup and recovery operations on databases that use ASM files is through Recovery Manager (RMAN).
    ASM is implemented as a separate Oracle instance that must be up if other databases are to be able to access it. Memory requirements for ASM are light: only 64 MB for most systems.
    Installing ASM
    On Linux platforms, ASM can use raw devices or devices managed via the ASMLib interface. Oracle recommends ASMLib over raw devices for ease-of-use and performance reasons. ASMLib 2.0 is available for free download from OTN. This section walks through the process of configuring a simple ASM instance by using ASMLib 2.0 and building a database that uses ASM for disk storage.
    Determine Which Version of ASMLib You Need
    ASMLib 2.0 is delivered as a set of three Linux packages:
    * oracleasmlib-2.0 - the ASM libraries
    * oracleasm-support-2.0 - utilities needed to administer ASMLib
    * oracleasm - a kernel module for the ASM library
    Each Linux distribution has its own set of ASMLib 2.0 packages, and within each distribution, each kernel version has a corresponding oracleasm package. The following paragraphs describe how to determine which set of packages you need.
    First, determine which kernel you are using by logging in as root and running the following command:
    uname -rm
    Ex:
    # uname -rm
    2.6.9-22.ELsmp i686
    The example shows that this is a 2.6.9-22 kernel for an SMP (multiprocessor) box using Intel i686 CPUs.
    Use this information to find the correct ASMLib packages on OTN:
    1. Point your Web browser to http://www.oracle.com/technology/tech/linux/asmlib/index.html
    2. Select the link for your version of Linux.
    3. Download the oracleasmlib and oracleasm-support packages for your version of Linux
    4. Download the oracleasm package corresponding to your kernel. In the example above, the oracleasm-2.6.9-22.ELsmp-2.0.0-1.i686.rpm package was used.
    Next, install the packages by executing the following command as root:
    rpm -Uvh oracleasm-kernel_version-asmlib_version.cpu_type.rpm \
    oracleasmlib-asmlib_version.cpu_type.rpm \
    oracleasm-support-asmlib_version.cpu_type.rpm
    Ex:
    # rpm -Uvh \
    > oracleasm-2.6.9-22.ELsmp-2.0.0-1.i686.rpm \
    > oracleasmlib-2.0.1-1.i386.rpm \
    > oracleasm-support-2.0.1-1.i386.rpm
    Preparing... ########################################### [100%]
    1:oracleasm-support ########################################### [ 33%]
    2:oracleasm-2.6.9-22.ELsm########################################### [ 67%]
    3:oracleasmlib ########################################### [100%]
    Configuring ASMLib
    Before using ASMLib, you must run a configuration script to prepare the driver. Run the following command as root, and answer the prompts as shown in the example below.
    # /etc/init.d/oracleasm configure
    Configuring the Oracle ASM library driver.
    This will configure the on-boot properties of the Oracle ASM library
    driver. The following questions will determine whether the driver is
    loaded on boot and what permissions it will have. The current values
    will be shown in brackets ('[]'). Hitting <ENTER> without typing an
    answer will keep that current value. Ctrl-C will abort.
    Default user to own the driver interface []: oracle
    Default group to own the driver interface []: dba
    Start Oracle ASM library driver on boot (y/n) [n]: y
    Fix permissions of Oracle ASM disks on boot (y/n) [y]: y
    Writing Oracle ASM library driver configuration: [  OK  ]
    Creating /dev/oracleasm mount point: [  OK  ]
    Loading module "oracleasm": [  OK  ]
    Mounting ASMlib driver filesystem: [  OK  ]
    Scanning system for ASM disks: [  OK  ]
    Next you tell the ASM driver which disks you want it to use. Oracle recommends that each disk contain a single partition for the entire disk. See Partitioning the Disks at the beginning of this section for an example of creating disk partitions.
    You mark disks for use by ASMLib by running the following command as root:
    /etc/init.d/oracleasm createdisk DISK_NAME device_name
    Tip: Enter the DISK_NAME in UPPERCASE letters.
    Ex:
    # /etc/init.d/oracleasm createdisk VOL1 /dev/sdb1
    Marking disk "/dev/sdb1" as an ASM disk: [  OK  ]
    # /etc/init.d/oracleasm createdisk VOL1 /dev/sdc1
    Marking disk "/dev/sdc1" as an ASM disk: [  OK  ]
    # /etc/init.d/oracleasm createdisk VOL1 /dev/sdd1
    Marking disk "/dev/sdd1" as an ASM disk: [  OK  ]
    Verify that ASMLib has marked the disks:
    # /etc/init.d/oracleasm listdisks
    VOL1
    VOL2
    VOL3
    Create the ASM Instance
    ASM runs as a separate Oracle instance which can be created and configured using the Oracle Universal Installer. Now that ASMLib is installed and the disks are marked for use, you can create an ASM instance.
    Log in as oracle and start runInstaller:
    $ ./runInstaller
    1. Select Installation Method
    * Select Advanced Installation
    * Click on Next
    2. Specify Inventory Directory and Credentials
    * Inventory Directory: /u01/app/oracle/oraInventory
    * Operating System group name: oinstall
    * Click on Next
    3. Select Installation Type
    * Select Enterprise Edition
    * Click on Next
    4. Specify Home Details
    * Name: OraDB10gASM
    * Path: /u01/app/oracle/product/10.2.0/asm
    Note:Oracle recommends using a different ORACLE_HOME for ASM than the ORACLE_HOME used for the database for ease of administration.
    * Click on Next
    5. Product-specific Prerequisite Checks
    * If you've been following the steps in this guide, all the checks should pass without difficulty. If one or more checks fail, correct the problem before proceeding.
    * Click on Next
    6. Select Configuration Option
    * Select Configure Automatic Storage Management (ASM)
    * Enter the ASM SYS password and confirm
    * Click on Next
    7. Configure Automatic Storage Management
    * Disk Group Name: DATA
    * Redundancy
    - High mirrors data twice.
    - Normal mirrors data once. This is the default.
    - External does not mirror data within ASM. This is typically used if an external RAID array is providing redundancy.
    * Add Disks
    The disks you configured for use with ASMLib are listed as Candidate Disks. Select each disk you wish to include in the disk group.
    * Click on Next
    8. Summary
    * A summary of the products being installed is presented.
    * Click on Install.
    9. Execute Configuration Scripts
    * At the end of the installation, a pop up window will appear indicating scripts that need to be run as root. Login as root and run the indicated scripts.
    * Click on OK when finished.
    10. Configuration Assistants
    * The Oracle Net, Oracle Database, and iSQL*Plus configuration assistants will run automatically
    11. End of Installation
    * Make note of the URLs presented in the summary, and click on Exit when ready.
    12. Congratulations! Your new Oracle ASM Instance is up and ready for use.
    Kind regards
    Mohamed

Maybe you are looking for

  • Added 2nd Hard Drive - Which Format Do I Select?

    I just added a 2nd hard drive. It shows up in disk utility. I know I must format it before I can use it. But, there are 6 choices in the Volume format drop down: Mac OS Extended (Journaled), Mac OS Extended , Mac OS Extended case - sensitive journale

  • How to rearrange the structure of a table by using a view?

    At wits end: I need to reorganize the structure of a table into a new structure - either as a view or actually moving the data from the old structure to the new structure (using a view). The old structure is: TESTNAME, SCHOOL_ID, PTILE1, PTILE2, PTIL

  • Over Flow Error

    Hi,    I am creating a functional module. In the global data, I had included a standard Include. include MM06ETOP_GLOBAL_DATA. When I am doing syntax check, it is showing ok. When i am activating it, it is giving the following error. Overflow when co

  • Weblogic server 12c managed server not starting

    Hi All, I am a newbie in weblogic. I downloaded the weblogic server 12c and installed in development mode in my Mac OSX 10.8. I am able to create the clusters and added the managed servers in it. I started the node manager attached to the machine whe

  • There is a estimated date for the new Mac Pro?

    Hi I'm going to buy a new Mac Pro in the next months, I'm trying to find if there is going to be a new mac pro to wait until then but i find almost no information. I would like to know if here i can find some. Thanks in advance