Schema Privilages in Portal

when i am trying to do new application i found this.
The database schemas that you can choose are those in which you have been granted privileges by the Oracle Portal DBA.
and the only seen accessed by user portal30 is scott.
when i am opening the DBA studio from the 9iAS it don't work.
how can i change the privilages.
thanks for your concern.

Gamal,
This question should be asked in the Oracle9iAS Portal Applications forum. Make sure to search the forum as I am pretty sure your question has already been answered.
Thanks,
Rich

Similar Messages

  • Changes to the color scheme in the portal

    Hi All
    I need to make changes to the color of the tab strip according to the customer's req. Now, there is no customer specific theme created and i think SAP chrome is in use.How should i accomplish the changes. Can you please guide me thru the steps to do so? In case i create a new theme , then how to make it an active theme.
    Please advise
    Thanks & regards

    Ankur,
    Check this video for step by step approach to create a theme.
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/4a10edf9-0701-0010-a6bc-c63bc3db08d5
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/e549a890-0201-0010-3f8b-d3b852457ebd
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/6483a890-0201-0010-48a6-b6e595111efe
    Cheers,
    Sandeep Tudumu
    P.S Consider rewarding for handy posts!
    Edited by: Sandeep Tudumu on Sep 22, 2008 2:47 PM
    Edited by: Sandeep Tudumu on Sep 22, 2008 2:49 PM

  • ERRORS IN PORTAL WHEN DROPPING SCHEMA OWNER

    I ran a PDK demo script and added 2 db packages to a schema in the portal repository. After running theses porlets, I decided to attempt to create my own. Prior to adding to the schema I wanted to clean out the old db packages. I thought the easy way would be to drop the user schema and recreate it clean. I attempted to drop the user schema by entering portal as orcladmin, clicking on navigator, then db objects, selected the schema I wanted to drop and it sat there for a few minutes and returned errors. I then opened SQLplus and dropped the user cascade. I noticed that the provider is still in the providers tab list, but can't delete it. I then attempted to re-create the schema using same name and I get additional errors in portal (see upload file: createrror2.jpg. I need to 1) drop the old provider and 2) recreate a new schema and provider that I will use for my portal/portlets.
    Any suggestions.

    I ran a PDK demo script and added 2 db packages to a schema in the portal repository. After running theses porlets, I decided to attempt to create my own. Prior to adding to the schema I wanted to clean out the old db packages. I thought the easy way would be to drop the user schema and recreate it clean. I attempted to drop the user schema by entering portal as orcladmin, clicking on navigator, then db objects, selected the schema I wanted to drop and it sat there for a few minutes and returned errors. I then opened SQLplus and dropped the user cascade. I noticed that the provider is still in the providers tab list, but can't delete it. I then attempted to re-create the schema using same name and I get additional errors in portal (see upload file: createrror2.jpg. I need to 1) drop the old provider and 2) recreate a new schema and provider that I will use for my portal/portlets.
    Any suggestions.

  • CANNOT GRANT A USER ACCESS TO VIEW A SCHEMA USING PORTAL API'S

    Hi, we are using portal 3.0.9.8.3(UNIX middle tier) on a 8.1.7.3 database (UNIX backend).
    We would like to be able to grant a group of users the rights to view only a specific table or view using the functionality of the wwexp_api_engine package. However the only way to do this seems to be to give the users "view data" privilege to "all schemas" within the portal admin. This presents a large security hole since users can could potentionaly pass in different table names (to a url) and get access to undesired tables.
    Granting executable privileges on the package(and sub packages) to the application database schema(whether public or explicit) still yields the above
    message: Error: Insufficient privileges. (WWV-10600)
    So does anyone know of a way to use the wwexp_api_engine package and restrict it to only a certain table or view of a schema? Or possibly what grants may be needed to allow the package to access the table without giving "view data" portal access to "all schemas".
    Any help would be appreciated.

    Hi,
    Try to grant "Create" global privilege to user and grant explicit privileges on the tables to the user. This way the user can create objects, but can view only those tables on which he has a privilege.
    Thanks,
    Sharmila

  • Schema procedures access in oracle portal

    Hi
    I have created a procedure under my schema and grant execute access to portal user. However, when I tried to execute the procedure from a report as portal user, it said procedure not found.
    When I created the same procedure under portal_public schema and the report works! Why is this so when I have already granted the right access? Please advice. Thanks!

    Thomas,
    First of all you need to create a schema for your Portal Application. Once that is done you will need to run in a DBA script called provsyns.sql so that this schema can execute and view the Portal core objects.
    This script is located in $9ias_ORACLE_HOME/portal30/admin/plsql/wwc
    Run this script as PORTAL30 with one parameter, this being the name of your new schema.
    Then your next step would be to set up all the necessary grants and synonyms so that the objects you wish to view over the gateway can be viewed from your application schema.
    Then you are ready to create an application in Portal via Navigator --> Applications.
    Choose the new schema as the Application schema (this is where all the Portal generated code gets compiled) and try creating a simple Report component to see if your non-portal components are set up properly.
    Hope this helps...
    John

  • OBE Portal lessons require HR Schema

    I am going through the OBE Portal (9.0.4) lessons, and several of them require a sample HR schema. How is this installed? I don't see an reference to installing this as a pre-req for the lessons.

    The HR Schema is a demo schema available with OracleAS Portal. You can see the HR schema in your Database Objects in Portal Navigator,if you have opted to install the demo schemas while installing OracleAS Portal.
    Please refer to this document (http://web51-01.oracle.com/docs/cd/B14099_01/portal.1012/b14134/pdg_portletbuilder.htm#BABIEDAG)
    on how to create a SCHEMA in OracleAS Portal.
    Create a Schema using the Database Objects tab in the Portal Navigator.
    Enter the name of the SCHEMA as HR. Provide a password and confirm it.
    The default tablespace should be PORTAL and the Temporary TableSpace should be Temp.
    Add the PORTAL.WWPRO_API_INVALIDATION object in the Grants tab in addition to the existing privileges.
    Now, you can use this schema to create your Database Provider.

  • HOW TO SET UP PARTNER APPLICATION TO USE SSO OUTSIDE OF PORTAL

    If anyone knows how Portal switches context to run as the db user mapped to the lightweight schema and how it knows the db schema password please let me know.
    Should you have any queries please do not hesitate to contact me on 07775 896738.
    From document Oracle Portal Security Overview on PortalStudio.oracle.com:
    In Single Sign On mode (EnableSSO=Yes in the DAD), mod_plsql determines the name of the light-weight user and mapped database schema by calling
    WPG_SESSION_PRIVATE.GET_LW_USER and WPG_SESSION_PRIVATE.GET_DB_USER respectively.
    ** These calls are done using the Portal Schema (PORTAL30) and Portal schema password **
    mod_plsql then executes the procedure in the requested URL by using the N-Tier Authentication feature to connect to the database as the user returned from
    WPG_SESSION_PRIVATE.GET_DB_USER. ..... Note that N-Tier Authentication requires all schemas to be used for Portal user mappings to be granted 'connect
    through' privleges to the Portal schema (PORTAL30).
    The WWCTX packages are also used.
    So this is how it works with standard Portal
    - the document states that the WPG_SESSION_PRIVATE package is only accessible to the Portal schema
    - but I checked and it is also available to PORTAL30_SSO
    SQL> desc WPG_SESSION_PRIVATE
    PROCEDURE CREATE_SESSION
    Argument Name Type In/Out Default?
    P_COOKIE_NAME VARCHAR2 IN
    FUNCTION GET_DB_USER RETURNS VARCHAR2
    FUNCTION GET_LW_USER RETURNS VARCHAR2
    PROCEDURE GET_SESSION_INFO
    Argument Name Type In/Out Default?
    NUM_PARAMS NUMBER OUT
    PARAM_NAMES TABLE OF VARCHAR2(32000) OUT
    PARAM_VALUES TABLE OF VARCHAR2(32000) OUT
    PROCEDURE RESET_SESSION
    Argument Name Type In/Out Default?
    P_COOKIE_NAME VARCHAR2 IN
    In my case only the Login Server (PORTAL30_SSO) is going to be used/installed
    - the SAMPLE_SSO_PAPP application will only work if the DAD used to access is it set to use Basic authentication, i.e. the actual integration with the Login Server
    is done in the sample application code calls, stored in the database
    - when a DAD has enableSSO=yes it automatically accesses Portal (PORTAL30) packages to implement N-Tier authentication
    I'm currently testing:
    1. Configuring the SAMPLE_SSO_PAPP sample as documented with a DAD with Basic authentication
    2. Amending the ssoapp procedure to set context to another (db) user on successful authentication:
    wwctx_api.set_context (
    p_user_name => 'SCOTT',
    p_password => 'TIGER' );
    3. If this works then set_context with get_lw_user instead
    I have now amended the ssoapp procedure as follows to print out
    1. The userid entered when the login box is presented
    2. The Database user which the Portal Lightweight user is mapped to
    3. The Lightweight user Portal has used for authentication
    Amendments to papp.pkb:
    (ssoapp procedure, declare db_user_info and lw_user_info as VARCHAR2 in declare section)
    htp.p('Congratulations! It is working!<br>');
    db_user_info := wwctx_api.get_db_user;
    lw_user_info := wwctx_api.get_user;
    htp.p('User Information:' || l_user_info || '<br>');
    htp.p('DB User Information:' || db_user_info || '<br>');
    htp.p('LW User Information:' || lw_user_info || '<br>');
    The following shows the interesting results from my testing:
    - if the user owning the sample_sso_papp package is PORTAL30_SSO then the call to wwctx_api.get_db_user succeeds
    - if the user owning the sample_sso_papp package is a non-portal schema e.g. SSOAPP below the call to wwctx_api.get_db_user generates a User Defined exception
    Steps to test:
    Created new schema SSOAPP on the database
    - edited it in Portal and checked the use this schema for Portal users checkbox
    - created new Lightweight user SSO_LW in Portal, mapped it to SSOAPP schema
    - created new Lightweight user SSO_SCOTT in Portal, mapped to SCOTT schema
    - loadjava -user ssoapp/ssoapp@portal30 SSOHash.class
    - sqlplus portal30/portal30@portal30
    @provsyns ssoapp
    - sqlplus ssoapp/ssoapp@portal30
    @loadsdk.sql
    @loadpapp.sql
    Created DAD with basic authentication SAMPLE_SSO_PAPP
    - username: ssoapp
    - default home page: sample_sso_papp.ssoapp
    Registered the Sample SSO Partner Application with the Login Server and ran regapp.sql
    Commented out the calls to get_db_user in papp.pkb to avoid exception
    - called http://<server>/pls/sample_sso_papp
    - logged on as SSO_LW/sso_lw
    - got output:
    Congratulations! It is working!
    User Information: SSO_LW
    LW User Information: PUBLIC
    So the Portal lightweight user is not returned as SSO_LW
    if anyone knows why the Lightweight User in my test is returned as PUBLIC not SSO_LW
    Best Regards
    MIchael

    http://support.mozilla.com/en-US/kb/Changing+the+e-mail+program+used+by+Firefox

  • How to call a PL/SQL procedure from Portal

    Env.Info: Windows NT Server 4 (Service Pack 3) / Oracle 8i R3 EE / Oracle Portal 3.0 Production.
    I created a new schema "BISAPPS" and created a user with the same name. Ran provsyns.sql script to grant Portal API access. Created a new package under this new schema and compiled it against the database. After that I registered the schema as a portal provider. There were no errors.
    Now I logged into Portal using the account PORTAL30. Refreshed the portlet repository and the new portlets appeared. I added the new portlet to the page. It is displayed successfully.
    New portlet allows the user to enter a bug-number and lets the user to either view or edit. If the user clicks on the button "Edit", it opens a new window and displays the contents from BugDB application. But if the user clicks on "Show", it should display the output generated by a PL/SQL procedure (Owned by the above New Schema - BISAPPS) in a separate window. But instead it is displaying the following error in the separate window:
    bisapps_pkg.buginfo: PROCEDURE DOESN'T EXIST.
    DAD name: PORTAL30
    PROCEDURE : bisapps_pkg.buginfo
    URL : http://host_name:80/pls/portal30/bisapps_pkg.buginfo
    And list of environment variables ....
    Can anyone help me? How can I call a PL/SQL procedure when the button is clicked? Thanks in advance.

    You must grant EXECUTE privilege on your procedure to the PORTAL30_PUBLIC user. If the error still persists, create a PUBLIC synonym for your procedure.

  • How to update Portal 10.1.2 to 10.1.4 under multiportal environment ?

    I install two portal and one infra.
    And Configuring Multiple Middle Tiers with a Load Balancing Router successfully.
    The origin portal virsion is 10.1.2.
    Now i want to update to 10.1.4 but have somthing wrong after I enter the update commond.
    Error message is java.SQLException: IO Exception : connection is reset.
    Then I run de upgrade command again , get the different error message
    ### ERROR: OracleAS Portal 10.1.4 upgrade precheck failed. See /raid/product/OraHome_1/upgrade/temp/portal/precheck.log for details.
    Error: Component upgrade failed PORTAL
    Error: PORTAL component version is: 10.1.2.0.2 INVALID
    FAILURE: Some OracleAS plug-ins report failure during upgrade.
    The Portal Upgrade precheck log is follow:
    -- Portal Upgrade release information: 10.1.4 Release 1
    Upgrade Started in -precheck -force mode at Wed Oct 18 21:22:19 2006
    ### PHASE 1: Initial setup
    Existing temporary directory /raid/product/OraHome_1/upgrade/temp/portal/prechktmp renamed to /raid/product/OraHome_1/upgrade/temp/portal/prechktmp.Wed-Oct-18-21.14.10-2006
    Existing log file /raid/product/OraHome_1/upgrade/temp/portal/precheck.log renamed to /raid/product/OraHome_1/upgrade/temp/portal/precheck.log.Wed-Oct-18-21.14.10-2006
    Creating /raid/product/OraHome_1/upgrade/temp/portal/prechktmp directory
    Creating /raid/product/OraHome_1/upgrade/temp/portal/prechktmp/gen directory
    Welcome to the Oracle Portal Production Upgrade
    The script will lead you through the upgrade step by step.
    For questions asked in this script that have appropriate defaults
    those defaults will be shown in square brackets after the question.
    To accept a default value, simply hit the Return key.
    ### Set New Variables and Validate Environment Variables
    Step started at Wed Oct 18 21:22:19 2006
    PERL5LIB set to ../../../perl/lib/site_perl/5.6.1/i686-linux:../../../perl/lib:../../../perl/lib/5.6.1
    Check SQL*Plus version
    Running upg/frwk/upchkpls.sql### Log shared and environment variables
    Step started at Wed Oct 18 21:22:19 2006
    Log file: /raid/product/OraHome_1/upgrade/temp/portal/precheck.log
    Log dir: /raid/product/OraHome_1/upgrade/temp/portal/prechktmp
    Profile dir: /raid/product/OraHome_1/upgrade/temp/portal/prechktmp/gen
    Verbose flag: 0
    Debug mode: 0
    Force flag: 1
    Nosave flag: 0
    Save flag: 1
    Repos flag: 0
    Compile flag: 0
    Oldver flag: 0
    isPatch flag: 0
    Will save Tables: 1
    Environment variables:
    ===========================================================
    DISPLAY: :0
    G_BROKEN_FILENAMES: 1
    HISTSIZE: 1000
    HOME: /home/oracle
    HOSTNAME: portal1.bizmatch.com.cn
    IBPATH: /usr/bin
    INPUTRC: /etc/inputrc
    KDEDIR: /usr
    LANG: en_US.UTF-8
    LC_CTYPE: en_US.UTF-8
    LD_ASSUME_KERNEL: 2.4.19
    LD_LIBRARY_PATH: /raid/product/OraHome_1/lib32:/raid/product/OraHome_1/lib:/raid/tmp/jdk/jre/lib/i386/client:/raid/tmp/jdk/jre/lib/i386:/raid/tmp/jdk/jre/../lib/i386:/raid/product/OraHome_1/lib32:/raid/product/OraHome_1/network/lib32:/raid/product/OraHome_1/lib:/raid/product/OraHome_1/network/lib:/raid/product/OraHome_1/lib:/usr/lib:/usr/local/lib
    LD_LIBRARY_PATH_64: /raid/product/OraHome_1/lib:/raid/product/OraHome_1/lib32:/raid/product/OraHome_1/network/lib32:/raid/product/OraHome_1/lib:/raid/product/OraHome_1/network/lib:
    LESSOPEN: |/usr/bin/lesspipe.sh %s
    LIBPATH: /raid/product/OraHome_1/lib32:/raid/product/OraHome_1/lib
    LOGNAME: oracle
    LS_COLORS: no=00:fi=00:di=00;34:ln=00;36:pi=40;33:so=00;35:bd=40;33;01:cd=40;33;01:or=01;05;37;41:mi=01;05;37;41:ex=00;32:*.cmd=00;32:*.exe=00;32:*.com=00;32:*.btm=00;32:*.bat=00;32:*.sh=00;32:*.csh=00;32:*.tar=00;31:*.tgz=00;31:*.arj=00;31:*.taz=00;31:*.lzh=00;31:*.zip=00;31:*.z=00;31:*.Z=00;31:*.gz=00;31:*.bz2=00;31:*.bz=00;31:*.tz=00;31:*.rpm=00;31:*.cpio=00;31:*.jpg=00;35:*.gif=00;35:*.bmp=00;35:*.xbm=00;35:*.xpm=00;35:*.png=00;35:*.tif=00;35:
    MAIL: /var/spool/mail/oracle
    NLSPATH: /usr/dt/lib/nls/msg/%L/%N.cat
    ORACLE_BASE: /raid/product
    ORACLE_HOME: /raid/product/OraHome_1
    ORACLE_SID:
    PATH: /raid/product/OraHome_1/bin:../../../perl/bin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/home/oracle/bin:/raid/product/OraHome_1/bin:/usr/local/sbin:/usr/bin/X11:/usr/X11R6/bin:/home/oracle/bin:/bin:/sbin:/usr/bin
    PERL5LIB: ../../../perl/lib/site_perl/5.6.1/i686-linux:../../../perl/lib:../../../perl/lib/5.6.1
    PWD: /raid/tmp/mrua
    QTDIR: /usr/lib/qt-3.3
    REPCA_ORACLE_HOME: /raid/tmp
    SHELL: /bin/bash
    SHLIB_PATH: /raid/product/OraHome_1/lib32:/raid/product/OraHome_1/lib
    SHLVL: 3
    SQLPATH: .:owa:/raid/product/OraHome_1/upgrade/temp/portal/prechktmp/gen:upg/frwk:sql:wwc
    SSH_ASKPASS: /usr/libexec/openssh/gnome-ssh-askpass
    TERM: xterm
    USER: oracle
    XAUTHORITY: /root/.Xauthority
    XFILESEARCHPATH: /usr/dt/app-defaults/%L/Dt
    _: /raid/tmp/jdk/bin/java
    ### PHASE 2: User inputs
    Upgrade phase started at Wed Oct 18 21:22:19 2006
    Processing Metadata File: upg/common/inputchk/inputchk.met Running upg/common/inputchk/inputchk.pl ### Verify that the database has been backed up
    Step started at Wed Oct 18 21:22:19 2006
    Before beginning the upgrade, it is important that you backup your database.
    Have you backed up your database (y/n)? [y]: y
    Ask user for schema and database details
    Enter the name of schema that you would like to upgrade [PORTAL]: portal
    Enter the password for the schema that you would like to upgrade [portal]:
    Enter the password for the SYS user of your database [CHANGE_ON_INSTALL]:
    Enter the TNS connect string to connect to the database [ORCL]: (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=portaldb.bizmatch.com.cn)(PORT=1521))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=IASDB.bizmatch.com.cn)))
    Responses to the above questions will now be recorded in the file
    upgrade.in. Placeholders are recorded instead of actual passwords,
    for security reasons. If you wish, this file can be edited and used
    as the standard input for a subsequent run of upgrade.pl.
    ### Verify database connection information.
    Step started at Wed Oct 18 21:22:19 2006
    Validating the connection information supplied by the user
    Running CheckConnections()Check connection to the Portal repository.
    Check connection as SYS to the Portal repository.
    Ending CheckConnections() Wed Oct 18 21:22:19 2006
    ### PHASE 3: Setup
    Upgrade phase started at Wed Oct 18 21:22:19 2006
    Processing Metadata File: upg/common/setup/setup.met Running upg/common/setup/setup.pl Analyzing the product schema
    Running upg/common/setup/upgettbs.sqlPortal SQL script started at Wed Oct 18 21:22:19 2006
    Connected.
    ### Install messaging framework
    Step started at Wed Oct 18 21:22:19 2006
    Portal SQL script started at Wed Oct 18 21:22:19 2006
    Connected.
    No errors.
    No errors.
    Creating sequence 'wwpof_output_id_seq'
    Creating sequence 'wwpof_output_script_run_id_seq'
    Creating table 'wwpof_output$'
    Creating table 'wwpof_msg$'
    Creating index 'wwpof_output_idx1' in tablespace PORTAL
    Creating index 'wwpof_output_idx2' in tablespace PORTAL
    Creating index 'wwpof_output_idx3' in tablespace PORTAL
    Creating index 'wwpof_msg_uk1' in tablespace PORTAL
    No errors.
    No errors.
    Granting privileges on POF objects to SYS
    Loading /raid/product/OraHome_1/upgrade/temp/portal/prechktmp/upgus.ctl using sqlldr
    Copying scripts to de-install message objects.
    Get Portal version and determine upgrade sequence
    Running upg/common/setup/upgetver.sqlPortal SQL script started at Wed Oct 18 21:22:22 2006
    Connected.
    Upgrading to version 10.1.4.0.0
    Version directories to be traversed: upg/10140
    Running upg/common/setup/setseq.pl Set the correct Traversal Sequence
    ### PHASE 4: Pre upgrade checks
    Upgrade phase started at Wed Oct 18 21:22:22 2006
    Processing Metadata File: upg/common/prechk/prechk.met Running upg/common/prechk/prechk.pl Set up subscriber iteration
    Running upg/common/prechk/upgetsub.sqlPortal SQL script started at Wed Oct 18 21:22:22 2006
    Connected.
    ### Perform pre upgrade checks
    Step started at Wed Oct 18 21:22:22 2006
    Running upg/frwk/utlchvpd.sqlPortal SQL script started at Wed Oct 18 21:22:22 2006
    Connected.
    Calling DoPreChecks()Starting precheck at Wed Oct 18 21:22:23 2006
    Calling upg/common/prechk/sysuppre.sql
    Connected.
    Running upg/common/prechk/upgtabs.sqlPortal SQL script started at Wed Oct 18 21:22:23 2006
    Connected.
    ### ERROR: WWU-00013: Tables with UPG_ prefix were found in the OracleAS Portal
    ### schema.
    ### Table Name
    ### UPG_PTL_OBJECTS$
    ### UPG_PTL_TABLES$
    ### UPG_WWV_DOCINFO
    ### CAUSE: The upgrade is terminated when UPG_ prefix tables are present in the
    ### OracleAS Portal schema.
    ### ACTION: Back up all tables with the UPG_ prefix, then delete them from the
    ### OracleAS Portal schema. The script
    ### /raid/product/OraHome_1/upgrade/temp/portal/prechktmp/dropupg.sql can
    ### be used for this purpose.
    ### Check Failed at Wed Oct 18 21:22:23 2006 Continuing as PreCheck mode is specified
    Calling upg/common/prechk/wwvcheck.sql
    Portal SQL script started at Wed Oct 18 21:22:23 2006
    Connected.
    # Beginning outer script: prechk/wwvcheck
    # Check for invalid Portlet Builder (webview) components.
    # Checking if there are too many archive components.
    # Checking for missing application schemas.
    # Ending outer script: prechk/wwvcheck, 0.31 seconds
    Ending precheck at Wed Oct 18 21:22:24 2006
    Running upg/common/prechk/upchkobj.sqlPortal SQL script started at Wed Oct 18 21:22:24 2006
    Connected.
    Running upg/common/prechk/chkmrreg.sqlPortal SQL script started at Wed Oct 18 21:22:24 2006
    Connected.
    # Beginning outer script: prechk/chkmrreg
    # Pre-check to determine that OracleAS Portal is registered with OracleAS Internet Directory
    # OracleAS Portal has been wired with OracleAS Internet Directory
    # Ending outer script: prechk/chkmrreg, 0.10 seconds
    ### Connect to OID as Application Entry
    Running upg/common/prechk/bindapp.sql . Portal SQL script started at Wed Oct 18 21:22:24 2006
    Connected.
    # Beginning outer script: prechk/bindapp
    #-- Beginning inner script: prechk/bindapp
    # Pre-check to test bind to OracleAS Internet Directory Server
    # Connecting to OracleAS Internet Directory as the Application Entry
    # Connecting to OracleAS Internet Directory as the Application Entry was successful
    #-- Ending inner script: prechk/bindapp, 0.14 seconds
    # Ending outer script: prechk/bindapp, 0.20 seconds
    ### Display Tablespace and Parameter Settings
    Running upg/common/prechk/../../frwk/upshoset.sql .
    Subscriber independent Processing.
    Portal SQL script started at Wed Oct 18 21:22:24 2006
    Connected.
    # Beginning outer script: prechk/upshoset
    Tablespace Usage
    TABLESPACE BYTES_USED BYTES_FREE TOTAL BYTES CREATE_BYTES AUT FILE STAT STATUS     ENABLED BLOCKS BLOCK_SIZE FILE_NAME
    B2B_DT     63766528     20054016 83886080          0 YES AVAILABLE ONLINE     READ WRITE     10240     8192 /raid/product/oradata/IASDB/b2b_dt.dbf
    B2B_IDX 14942208     26935296 41943040          0 YES AVAILABLE ONLINE     READ WRITE     5120     8192 /raid/product/oradata/IASDB/b2b_idx.dbf
    B2B_LOB 11141120     30736384 41943040          0 YES AVAILABLE ONLINE     READ WRITE     5120     8192 /raid/product/oradata/IASDB/b2b_lob.dbf
    B2B_RT     39780352     12582912 52428800          0 YES AVAILABLE ONLINE     READ WRITE     6400     8192 /raid/product/oradata/IASDB/b2b_rt.dbf
    BAM     6553600     3866624 10485760          0 YES AVAILABLE ONLINE     READ WRITE     1280     8192 /raid/product/oradata/IASDB/bam.dbf
    DCM     237174784     20709376 257949696          0 YES AVAILABLE ONLINE     READ WRITE     31488     8192 /raid/product/oradata/IASDB/dcm.dbf
    DISCO_PTM5 1310720     1769472 3145728          0 YES AVAILABLE ONLINE     READ WRITE     384     8192 /raid/product/oradata/IASDB/discopltc1.dbf
    _CACHE
    DISCO_PTM5 1310720     1769472 3145728          0 YES AVAILABLE ONLINE     READ WRITE     384     8192 /raid/product/oradata/IASDB/discopltm1.dbf
    _META
    DSGATEWAY_ 5701632     1572864 7340032          0 YES AVAILABLE ONLINE     READ WRITE     896     8192 /raid/product/oradata/IASDB/oss_sys01.dbf
    TAB
    IAS_META 210567168     30539776 241172480          0 YES AVAILABLE ONLINE     READ WRITE     29440     8192 /raid/product/oradata/IASDB/ias_meta01.dbf
    OCATS     1769472     5505024 7340032          0 YES AVAILABLE ONLINE     READ WRITE     896     8192 /raid/product/oradata/IASDB/oca.dbf
    OLTS_ATTRS 2555904     917504 3538944          0 YES AVAILABLE ONLINE     READ WRITE     432     8192 /raid/product/oradata/IASDB/attrs1_oid.dbf
    TORE
    OLTS_BATTR 262144     131072 516096          0 YES AVAILABLE ONLINE     READ WRITE     63     8192 /raid/product/oradata/IASDB/battrs1_oid.dbf
    STORE
    OLTS_DEFAU 3997696     851968 4915200          0 YES AVAILABLE ONLINE     READ WRITE     600     8192 /raid/product/oradata/IASDB/gdefault1_oid.dbf
    LT
    ORABPEL 11993088     29884416 41943040          0 YES AVAILABLE ONLINE     READ WRITE     5120     8192 /raid/product/oradata/IASDB/orabpel.dbf
    PORTAL     74383360     6946816 78643200          0 YES AVAILABLE ONLINE     READ WRITE     9600     8192 /raid/product/oradata/IASDB/portal.dbf
    PORTAL_DOC 851968     3276800 4194304          0 YES AVAILABLE ONLINE     READ WRITE     512     8192 /raid/product/oradata/IASDB/ptldoc.dbf
    PORTAL_IDX 11206656     41156608 52428800          0 YES AVAILABLE ONLINE     READ WRITE     6400     8192 /raid/product/oradata/IASDB/ptlidx.dbf
    PORTAL_LOG 262144     3866624 4194304          0 YES AVAILABLE ONLINE     READ WRITE     512     8192 /raid/product/oradata/IASDB/ptllog.dbf
    SYSAUX     235732992     5373952 241172480          0 YES AVAILABLE ONLINE     READ WRITE     29440     8192 /raid/product/oradata/IASDB/sysaux01.dbf
    SYSTEM     834404352     4390912 838860800          0 YES AVAILABLE SYSTEM     READ WRITE 102400     8192 /raid/product/oradata/IASDB/system01.dbf
    TEMP     6291456     18874368 25165824     25165824 YES AVAILABLE ONLINE     READ WRITE     3072     8192 /raid/product/oradata/IASDB/temp01.dbf
    UDDISYS_TS 19988480     28180480 48234496          0 YES AVAILABLE ONLINE     READ WRITE     5888     8192 /raid/product/oradata/IASDB/uddisys01.dbf
    UNDOTBS1 247201792     4390912 251658240          0 YES AVAILABLE ONLINE     READ WRITE     30720     8192 /raid/product/oradata/IASDB/undotbs01.dbf
    USERS     327680     4849664 5242880          0 YES AVAILABLE ONLINE     READ WRITE     640     8192 /raid/product/oradata/IASDB/users01.dbf
    WCRSYS_TS 1703936     15007744 16777216          0 YES AVAILABLE ONLINE     READ WRITE     2048     8192 /raid/product/oradata/IASDB/wcrsys01.dbf
    Sort Segment Data
    TABLESPACE EXTENT_SIZE TOTAL_EXTENTS USED_EXTENTS FREE_EXTENTS MAX_USED_SIZE
    TEMP          128          5          0     5          1
    SGA Allocation Stats
    POOL     NAME                    BYTES
    java pool free memory               67108864
    Total                              67108864
    SGA Allocation Stats
    POOL     NAME                    BYTES
    large pool free memory               8388608
    Total                              8388608
    SGA Allocation Stats
    POOL     NAME                    BYTES
    shared pool fixed allocation callback               344
    shared pool pl/sql source               1156
    shared pool table definiti               1712
    shared pool alert threshol               2648
    shared pool trigger inform               3048
    shared pool joxs heap                    4220
    shared pool policy hash ta               4220
    shared pool trigger defini               5980
    shared pool KQR S SO                    7176
    shared pool PLS non-lib hp               12208
    shared pool trigger source               18652
    shared pool KQR L SO                    44032
    shared pool repository                76264
    shared pool KQR M SO                    81408
    shared pool parameters                105696
    shared pool type object de               194164
    shared pool KQR S PO                    207136
    shared pool VIRTUAL CIRCUITS               649340
    shared pool FileOpenBlock               746704
    shared pool kmgsb circular statistics          821248
    shared pool KSXR pending messages que          841036
    shared pool KSXR receive buffers          1032500
    shared pool KQR M PO                    1675892
    shared pool sessions                    1835204
    shared pool PL/SQL DIANA               2910560
    shared pool private strands               2928640
    shared pool KTI-UNDO                    3019632
    shared pool KGLS heap                    3105320
    shared pool PL/SQL MPCODE               3705484
    shared pool row cache                    3707272
    shared pool ASH buffers               4194304
    shared pool event statistics per sess          9094400
    shared pool sql area                    9234624
    shared pool library cache               10361688
    shared pool miscellaneous               15820288
    shared pool free memory               74540744
    Total                              150994944
    SGA Allocation Stats
    POOL     NAME                    BYTES
         log_buffer                524288
         fixed_sga                    778968
         buffer_cache               50331648
    Total                              51634904
    Database Parameters
    NAME                    VALUE
    O7_DICTIONARY_ACCESSIBILITY     FALSE
    active_instance_count
    aq_tm_processes           1
    archive_lag_target          0
    asm_diskgroups
    asm_diskstring
    asm_power_limit           1
    audit_file_dest           /raid/product/OraHome_1/rdbms/audit
    audit_sys_operations          FALSE
    audit_trail               NONE
    background_core_dump          partial
    background_dump_dest          /raid/product/admin/IASDB/bdump
    backup_tape_io_slaves          FALSE
    bitmap_merge_area_size          1048576
    blank_trimming               FALSE
    buffer_pool_keep
    buffer_pool_recycle
    circuits
    cluster_database          FALSE
    cluster_database_instances     1
    cluster_interconnects
    commit_point_strength          1
    compatible               10.1.0.2.0
    control_file_record_keep_time     7
    control_files               /raid/product/oradata/IASDB/control01.ctl, /raid/product/oradata/IASDB/control02
                        .ctl, /raid/product/oradata/IASDB/control03.ctl
    core_dump_dest               /raid/product/admin/IASDB/cdump
    cpu_count               2
    create_bitmap_area_size      8388608
    create_stored_outlines
    cursor_sharing               EXACT
    cursor_space_for_time          FALSE
    db_16k_cache_size          0
    db_2k_cache_size          0
    db_32k_cache_size          0
    db_4k_cache_size          0
    db_8k_cache_size          0
    db_block_buffers          0
    db_block_checking          FALSE
    db_block_checksum          TRUE
    db_block_size               8192
    db_cache_advice           ON
    db_cache_size               50331648
    db_create_file_dest
    db_create_online_log_dest_1
    db_create_online_log_dest_2
    db_create_online_log_dest_3
    db_create_online_log_dest_4
    db_create_online_log_dest_5
    db_domain               bizmatch.com.cn
    db_file_multiblock_read_count     16
    db_file_name_convert
    db_files               200
    db_flashback_retention_target     1440
    db_keep_cache_size          0
    db_name                IASDB
    db_recovery_file_dest          /raid/product/flash_recovery_area
    db_recovery_file_dest_size     2147483648
    db_recycle_cache_size          0
    db_unique_name               IASDB
    db_writer_processes          1
    dbwr_io_slaves               0
    ddl_wait_for_locks          FALSE
    dg_broker_config_file1          /raid/product/OraHome_1/dbs/dr1IASDB.dat
    dg_broker_config_file2          /raid/product/OraHome_1/dbs/dr2IASDB.dat
    dg_broker_start           FALSE
    disk_asynch_io               TRUE
    dispatchers               (PROTOCOL=TCP)(PRE=oracle.aurora.server.GiopServer), (PROTOCOL=TCP)(PRE=oracle.a
                        urora.server.SGiopServer)
    distributed_lock_timeout     60
    dml_locks               1760
    drs_start               FALSE
    enqueue_resources          1980
    event
    fal_client
    fal_server
    fast_start_io_target          0
    fast_start_mttr_target          0
    fast_start_parallel_rollback     LOW
    file_mapping               FALSE
    fileio_network_adapters
    filesystemio_options          none
    fixed_date
    gc_files_to_locks
    gcs_server_processes          0
    global_context_pool_size
    global_names               FALSE
    hash_area_size               131072
    hi_shared_memory_address     0
    hs_autoregister           TRUE
    ifile
    instance_groups
    instance_name               IASDB
    instance_number           0
    instance_type               RDBMS
    java_max_sessionspace_size     0
    java_pool_size               67108864
    java_soft_sessionspace_limit     0
    job_queue_processes          5
    large_pool_size           8388608
    ldap_directory_access          NONE
    license_max_sessions          0
    license_max_users          0
    license_sessions_warning     0
    local_listener
    lock_name_space
    lock_sga               FALSE
    log_archive_config
    log_archive_dest
    log_archive_dest_1
    log_archive_dest_10
    log_archive_dest_2
    log_archive_dest_3
    log_archive_dest_4
    log_archive_dest_5
    log_archive_dest_6
    log_archive_dest_7
    log_archive_dest_8
    log_archive_dest_9
    log_archive_dest_state_1     enable
    log_archive_dest_state_10     enable
    log_archive_dest_state_2     enable
    log_archive_dest_state_3     enable
    log_archive_dest_state_4     enable
    log_archive_dest_state_5     enable
    log_archive_dest_state_6     enable
    log_archive_dest_state_7     enable
    log_archive_dest_state_8     enable
    log_archive_dest_state_9     enable
    log_archive_duplex_dest
    log_archive_format          %t_%s_%r.dbf
    log_archive_local_first      TRUE
    log_archive_max_processes     2
    log_archive_min_succeed_dest     1
    log_archive_start          FALSE
    log_archive_trace          0
    log_buffer               524288
    log_checkpoint_interval      0
    log_checkpoint_timeout          1800
    log_checkpoints_to_alert     FALSE
    log_file_name_convert
    logmnr_max_persistent_sessions     1
    max_commit_propagation_delay     0
    max_dispatchers
    max_dump_file_size          UNLIMITED
    max_enabled_roles          150
    max_shared_servers
    nls_calendar
    nls_comp
    nls_currency
    nls_date_format
    nls_date_language
    nls_dual_currency
    nls_iso_currency
    nls_language               AMERICAN
    nls_length_semantics          BYTE
    nls_nchar_conv_excp          FALSE
    nls_numeric_characters
    nls_sort
    nls_territory               AMERICA
    nls_time_format
    nls_time_tz_format
    nls_timestamp_format
    nls_timestamp_tz_format
    object_cache_max_size_percent     10
    object_cache_optimal_size     102400
    olap_page_pool_size          0
    open_cursors               300
    open_links               4
    open_links_per_instance      4
    optimizer_dynamic_sampling     2
    optimizer_features_enable     10.1.0.5
    optimizer_index_caching      0
    optimizer_index_cost_adj     100
    optimizer_mode               ALL_ROWS
    os_authent_prefix          ops$
    os_roles               FALSE
    parallel_adaptive_multi_user     TRUE
    parallel_automatic_tuning     FALSE
    parallel_execution_message_size 2148
    parallel_instance_group
    parallel_max_servers          40
    parallel_min_percent          0
    parallel_min_servers          0
    parallel_server           FALSE
    parallel_server_instances     1
    parallel_threads_per_cpu     2
    pga_aggregate_target          33554432
    plsql_code_type           INTERPRETED
    plsql_compiler_flags          INTERPRETED, NON_DEBUG
    plsql_debug               FALSE
    plsql_native_library_dir
    plsql_native_library_subdir_count 0
    plsql_optimize_level          2
    plsql_v2_compatibility          FALSE
    plsql_warnings               DISABLE:ALL
    pre_page_sga               FALSE
    processes               150
    query_rewrite_enabled          TRUE
    query_rewrite_integrity      enforced
    rdbms_server_dn
    read_only_open_delayed          FALSE
    recovery_parallelism          0
    remote_archive_enable          true
    remote_dependencies_mode     TIMESTAMP
    remote_listener
    remote_login_passwordfile     EXCLUSIVE
    remote_os_authent          FALSE
    remote_os_roles           FALSE
    replication_dependency_tracking TRUE
    resource_limit               FALSE
    resource_manager_plan
    resumable_timeout          0
    rollback_segments
    serial_reuse               disable
    service_names               IASDB.bizmatch.com.cn
    session_cached_cursors          0
    session_max_open_files          10
    sessions               400
    sga_max_size               281018368
    sga_target               0
    shadow_core_dump          partial
    shared_memory_address          0
    shared_pool_reserved_size     7549747
    shared_pool_size          150994944
    shared_server_sessions
    shared_servers               1
    skip_unusable_indexes          TRUE
    smtp_out_server
    sort_area_retained_size      0
    sort_area_size               65536
    sp_name                IASDB
    spfile                    /raid/product/OraHome_1/dbs/spfileIASDB.ora
    sql92_security               FALSE
    sql_trace               FALSE
    sql_version               NATIVE
    sqltune_category          DEFAULT
    standby_archive_dest          ?/dbs/arch
    standby_file_management      MANUAL
    star_transformation_enabled     FALSE
    statistics_level          TYPICAL
    streams_pool_size          0
    tape_asynch_io               TRUE
    thread                    0
    timed_os_statistics          0
    timed_statistics          TRUE
    trace_enabled               TRUE
    tracefile_identifier
    transactions               440
    transactions_per_rollback_segment 5
    undo_management           AUTO
    undo_retention               900
    undo_tablespace           UNDOTBS1
    use_indirect_data_buffers     FALSE
    user_dump_dest               /raid/product/admin/IASDB/udump
    utl_file_dir
    workarea_size_policy          AUTO
    All Portal DBMS jobs
    JOB LOG_USER          PRIV_USER     SCHEMA_USER
         17 PORTAL          PORTAL          PORTAL
         18 PORTAL          PORTAL          PORTAL
         27 PORTAL          PORTAL          PORTAL
         28 PORTAL          PORTAL          PORTAL
         43 PORTAL          PORTAL          PORTAL
    Details of all Portal DBMS jobs
    JOB WHAT
         17 begin execute immediate     'begin wwctx_sso.cleanup_sessions(
         p_hours_old => 168     ); end;'     ; exception     when others then
         null; end;
         18 wwsec_api_private.rename_users;
         27 wwv_context.sync;
         28 wwv_context.optimize(CTX_DDL.OPTLEVEL_FULL,1440,null);
         43 begin execute immediate     'begin wwutl_cache_sys.process_background_inv
         al;     end;'     ; exception     when others then     wwlog_api.log(p_
         domain=>'utl',     p_subdomain=>'cache',          p_name=>'background
         ',          p_action=>'process_background_inval',      p_information =
         > 'Error in process_background_inval '||          sqlerrm);end;
    Database version details
    BANNER
    Oracle Database 10g Enterprise Edition Release 10.1.0.4.2 - Prod
    PL/SQL Release 10.1.0.4.2 - Production
    CORE     10.1.0.4.0     Production
    TNS for Linux: Version 10.1.0.4.0 - Production
    NLSRTL Version 10.1.0.4.2 - Production
    # Ending outer script: prechk/upshoset, 1.83 seconds
    ### Log invalid DB objects in the temporary directory.
    List count of invalid objects in the database in /raid/product/OraHome_1/upgrade/temp/portal/prechktmp/dbinvob1.log
    Running upg/frwk/dbinvobj.sqlPortal SQL script started at Wed Oct 18 21:22:26 2006
    Connected.
    ### Install Schema Validation Utility
    Running upg/common/prechk/svuver.sql . Portal SQL script started at Wed Oct 18 21:22:26 2006
    Connected.
    # Beginning outer script: prechk/svuver
    #-- Beginning inner script: prechk/svuver
    # Portal Schema Version = 10.1.2.0.2
    # Version of schema validation utility being installed = 101202
    # Load the Schema Validation Utility
    Installed version of schema validation utility: 10.1.2.0.6
    Schema Validation Utility version: 10.1.2.0.6 will be installed.
    No errors.
    No errors.
    No errors.
    No errors.
    No errors.
    No errors.
    No errors.
    No errors.
    No errors.
    No errors.
    No errors.
    No errors.
    No errors.
    No errors.
    No errors.
    No errors.
    No errors.
    Warning: Package Body created with compilation errors.
    Errors for PACKAGE BODY WWUTL_SCHEMA_COMMON:
    44/9     PL/SQL: Statement ignored
    44/16     PLS-00905: object PORTAL.WWSBR_SITE_DB is invalid
    70/9     PL/SQL: Statement ignored
    70/17     PLS-00905: object PORTAL.WWPOB_API_PAGE is invalid
    96/10     PL/SQL: Statement ignored
    96/18     PLS-00905: object PORTAL.WWV_THINGDB is invalid
    122/10     PL/SQL: Statement ignored
    122/18     PLS-00905: object PORTAL.WWV_THINGDB is invalid
    No errors.
    Warning: Package Body created with compilation errors.
    Errors for PACKAGE BODY WWUTL_ATTR_VALIDATION:
    740/9     PL/SQL: SQL Statement ignored
    778/26     PL/SQL: ORA-06575: Package or function WWSBR_SITE_DB is in an
         invalid state
    Warning: Package Body created with compilation errors.
    Errors for PACKAGE BODY WWUTL_PAGE_GROUP_VALIDATION:
    366/9     PL/SQL: SQL Statement ignored
    372/31     PL/SQL: ORA-06575: Package or function WWSBR_SITE_DB is in an
         invalid state
    1447/13 PL/SQL: SQL Statement ignored
    1458/28 PL/SQL: ORA-06575: Package or function WWSBR_SITE_DB is in an
         invalid state
    1624/13 PL/SQL: SQL Statement ignored
    1635/28 PL/SQL: ORA-06575: Package or function WWSBR_SITE_DB is in an
         invalid state
    1783/13 PL/SQL: SQL Statement ignored
    1794/28 PL/SQL: ORA-06575: Package or function WWSBR_SITE_DB is in an
         invalid state
    1896/13 PL/SQL: SQL Statement ignored
    1907/28 PL/SQL: ORA-06575: Package or function WWSBR_SITE_DB is in an
         invalid state
    2009/13 PL/SQL: SQL Statement ignored
    2020/28 PL/SQL: ORA-06575: Package or function WWSBR_SITE_DB is in an
         invalid state
    2126/13 PL/SQL: SQL Statement ignored
    2137/28 PL/SQL: ORA-06575: Package or function WWSBR_SITE_DB is in an
         invalid state
    No errors.
    No errors.
    Warning: Package Body created with compilation errors.
    Errors for PACKAGE BODY WWUTL_PAGE_VALIDATION:
    137/9     PL/SQL: SQL Statement ignored
    144/53     PL/SQL: ORA-06575: Package or function WWSBR_SITE_DB is in an
         invalid state
    258/21     PL/SQL: SQL Statement ignored
    260/43     PL/SQL: ORA-06575: Package or function WWSBR_SITE_DB is in an
         invalid state
    277/17     PL/SQL: SQL Statement ignored
    279/39     PL/SQL: ORA-06575: Package or function WWSBR_SITE_DB is in an
         invalid state
    322/9     PL/SQL: SQL Statement ignored
    327/25     PL/SQL: ORA-06575: Package or function WWSBR_SITE_DB is in an
         invalid state
    353/25     PL/SQL: Statement ignored
    353/40     PLS-00905: object PORTAL.WWPOB_API_PAGE is invalid
    362/29     PL/SQL: SQL Statement ignored
    369/42     PL/SQL: ORA-06575: Package or function WWPOB_API_PAGE is in an
         invalid state
    376/33     PL/SQL: Statement ignored
    376/48     PLS-00905: object PORTAL.WWPOB_API_PAGE is invalid
    385/21     PL/SQL: SQL Statement ignored
    388/39     PL/SQL: ORA-06575: Package or function WWSBR_SITE_DB is in an
         invalid state
    1214/21 PL/SQL: SQL Statement ignored
    1216/42 PL/SQL: ORA-06575: Package or function WWSBR_SITE_DB is in an
         invalid state
    1262/9     PL/SQL: SQL Statement ignored
    1266/30 PL/SQL: ORA-06575: Package or function WWPOB_API_PAGE is in an
         invalid state
    Warning: Package Body created with compilation errors.
    Errors for PACKAGE BODY WWUTL_REGION_VALIDATION:
    237/9     PL/SQL: SQL Statement ignored
    249/41     PL/SQL: ORA-06575: Package or function WWSBR_SITE_DB is in an
         invalid state
    Warning: Package Body created with compilation errors.
    Errors for PACKAGE BODY WWUTL_STYLE_VALIDATION:
    414/9     PL/SQL: SQL Statement ignored
    424/44     PL/SQL: ORA-06575: Package or function WWSBR_SITE_DB is in an
         invalid state
    584/21     PL/SQL: Statement ignored
    584/52     PLS-00905: object PORTAL.WWSBR_SITE_DB is invalid
    Warning: Package Body created with compilation errors.
    Errors for PACKAGE BODY WWUTL_THING_VALIDATION:
    2129/32 PL/SQL: Item ignored
    2130/13 PLS-00905: object PORTAL.WWSBR_THING_TYPES is invalid
    2131/32 PL/SQL: Item ignored
    2132/13 PLS-00905: object PORTAL.WWSBR_THING_TYPES is invalid
    2133/32 PL/SQL: Item ignored
    2134/13 PLS-00905: object PORTAL.WWSBR_THING_TYPES is invalid
    2135/31 PL/SQL: Item ignored
    2136/13 PLS-00905: object PORTAL.WWSBR_THING_TYPES is invalid
    2137/31 PL/SQL: Item ignored
    2138/13 PLS-00905: object PORTAL.WWSBR_THING_TYPES is invalid
    2139/31 PL/SQL: Item ignored
    2140/13 PLS-00905: object PORTAL.WWSBR_THING_TYPES is invalid
    2151/32 PL/SQL: Item ignored
    2151/42 PLS-00320: the declaration of the type of this expression is
         incomplete or malformed
    2152/32 PL/SQL: Item ignored
    2152/42 PLS-00320: the declaration of the type of this expression is
         incomplete or malformed
    2153/32 PL/SQL: Item ignored
    2153/42 PLS-00320: the declaration of the type of this expression is
         incomplete or malformed
    2202/17 PL/SQL: SQL Statement ignored
    2212/27 PL/SQL: ORA-06575: Package or function WWSBR_THING_TYPES is in an
         invalid state
    Warning: Package Body created with compilation errors.
    Errors for PACKAGE BODY WWUTL_ITEM_VALIDATION:
    322/9     PL/SQL: SQL Statement ignored
    338/30     PL/SQL: ORA-06575: Package or function WWPOB_API_PAGE is in an
         invalid state
    Warning: Package Body created with compilation errors.
    Errors for PACKAGE BODY WWUTL_PORTLET_VALIDATION:
    155/13     PL/SQL: SQL Statement ignored
    163/36     PL/SQL: ORA-06575: Package or function WWSBR_SITE_DB is in an
         invalid state
    170/13     PL/SQL: SQL Statement ignored
    178/36     PL/SQL: ORA-06575: Package or function WWSBR_SITE_DB is in an
         invalid state
    459/9     PL/SQL: SQL Statement ignored
    467/31     PL/SQL: ORA-06575: Package or function WWSBR_SITEBUILDER_PROVIDER
         is in an invalid state
    581/9     PL/SQL: SQL Statement ignored
    584/21     PL/SQL: ORA-06575: Package or function WWSBR_SITEBUILDER_PROVIDER
         is in an invalid state
    588/9     PL/SQL: SQL Statement ignored
    591/29     PL/SQL: ORA-06575: Package or function WWSBR_SITEBUILDER_PROVIDER
         is in an invalid state
    Warning: Package Body created with compilation errors.
    Errors for PACKAGE BODY WWUTL_DBPROV_VALIDATION:
    341/25     PL/SQL: Item ignored
    341/45     PLS-00302: component 'URL' must be declared
    559/17     PL/SQL: Statement ignored
    559/17     PLS-00320: the declaration of the type of this expression is
         incomplete or malformed
    562/17     PL/SQL: Statement ignored
    564/40     PLS-00320: the declaration of the type of this expression is
         incomplete or malformed
    No errors.
    No errors.
    ### Invoke Schema Validation Utility in Report Mode
    Running upg/common/prechk/../../frwk/svurun.sql . Portal SQL script started at Wed Oct 18 21:22:31 2006
    Connected.
    # Beginning outer script: prechk/svurun
    #-- Beginning inner script: frwk/svurun
    declare
    ERROR at line 1:
    ORA-20000:
    ORA-06512: at "PORTAL.WWPOF", line 440
    ORA-06512: at line 45
    ORA-20000:
    ORA-06512: at "PORTAL.WWPOF", line 440
    ORA-06512: at "PORTAL.WWUTL_SCHEMA_VALIDATION", line 263
    ORA-04063: package body "PORTAL.WWUTL_PAGE_GROUP_VALIDATION" has errors
    ORA-06508: PL/SQL: could not find program unit being called
    Connected.
    # Run the report mode of the schema validation utility
    #---- Beginning inner script: wwutl_schema_validation.validate_all
    # Running the validation in report mode
    # Schema Validation Utility Version = 10.1.2.0.6
    # Validate Page Groups
    # Handling exception
    # ERROR: When executing schema validation utility
    # ERROR: ORA-06508: PL/SQL: could not find program unit being called
    # ----- PL/SQL Call Stack -----
    object line object
    handle number name
    0x5c4fef28     434 package body PORTAL.WWPOF
    0x5bb96e20     263 package body PORTAL.WWUTL_SCHEMA_VALIDATION
    0x5bb96e20     297 package body PORTAL.WWUTL_SCHEMA_VALIDATION
    0x5b885fe4     18 anonymous block
    # Handling exception
    # ERROR: When running the schema validation utility
    # ERROR: ORA-20000:
    ORA-06512: at "PORTAL.WWPOF", line 440
    ORA-06512: at "PORTAL.WWUTL_SCHEMA_VALIDATION", line 263
    ORA-04063: package body "PORTAL.WWUTL_PAGE_GROUP_VALIDATION" has errors
    ORA-06508: PL/SQL: could not find program unit being called
    # ----- PL/SQL Call Stack -----
    object line object
    handle number name
    0x5c4fef28     434 package body PORTAL.WWPOF
    0x5b885fe4     45 anonymous block
    ### ERROR: Exception Executing upg/common/prechk/../../frwk/svurun.sql REPORT PRECHK for Subscriber: 1
    ### Check Failed at Wed Oct 18 21:22:31 2006 Continuing as PreCheck mode is specified
    ### PHASE 5: Version specific user inputs
    Upgrade phase started at Wed Oct 18 21:22:31 2006
    Processing Metadata File: upg/10140/inputchk/inputchk.met ###
    ### PHASE 6: Version specific pre upgrade checks
    Upgrade phase started at Wed Oct 18 21:22:31 2006
    Processing Metadata File: upg/10140/prechk/prechk.met ###
    ### PHASE 7: Pre upgrade common information gathering
    Upgrade phase started at Wed Oct 18 21:22:31 2006
    Processing Metadata File: upg/common/info/info.met ### Log portal configuration info in the temporary directory.
    Running upg/common/info/ptlinfo.sql . Portal SQL script started at Wed Oct 18 21:22:31 2006
    Connected.
    # Beginning outer script: info/ptlinfo
    # Ending outer script: info/ptlinfo, 0.13 seconds
    Metadata File upg/10140/info/info.met does not exist.
    ### PHASE 8: Verify user inputs
    Upgrade phase started at Wed Oct 18 21:22:32 2006
    Processing Metadata File: upg/common/verfyinp/verfyinp.met Running upg/common/verfyinp/verfyinp.pl The following details have been determined:
    General Details
    ===========================================================
    Log File Name : /raid/product/OraHome_1/upgrade/temp/portal/precheck.log
    RDBMS Version : 10.1.0
    Product Version : 10.1.2.0.2
    Oracle PL/SQL Toolkit Schema : SYS
    Oracle PL/SQL Toolkit version : 10.1.2.0.2
    O7 accessibility : FALSE
    Schema Details
    ===========================================================
    Name : portal
    Connect String : (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=portaldb.bizmatch.com.cn)(PORT=1521))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=IASDB.bizmatch.com.cn)))
    Tablespace Details
    ===========================================================
    Default Tablespace : PORTAL
    Temporary Tablespace : TEMP
    Document Tablespace : PORTAL_DOC
    Logging Tablespace : PORTAL_LOG
    Index Tablespace : PORTAL
    ### ERROR: WWU-00030: Pre-Check mode encountered the following errors:
    ### 184 : ### ERROR: WWU-00013: Tables with UPG_ prefix were found in the OracleAS Portal
    ### 706 : 44/16     PLS-00905: object PORTAL.WWSBR_SITE_DB is invalid
    ### 708 : 70/17     PLS-00905: object PORTAL.WWPOB_API_PAGE is invalid
    ### 710 : 96/18     PLS-00905: object PORTAL.WWV_THINGDB is invalid
    ### 712 : 122/18     PLS-00905: object PORTAL.WWV_THINGDB is invalid
    ### 719 : 778/26     PL/SQL: ORA-06575: Package or function WWSBR_SITE_DB is in an
    ### 727 : 372/31     PL/SQL: ORA-06575: Package or function WWSBR_SITE_DB is in an
    ### 731 : 1458/28 PL/SQL: ORA-06575: Package or function WWSBR_SITE_DB is in an
    ### 735 : 1635/28 PL/SQL: ORA-06575: Package or function WWSBR_SITE_DB is in an
    ### 739 : 1794/28 PL/SQL: ORA-06575: Package or function WWSBR_SITE_DB is in an
    ### 743 : 1907/28 PL/SQL: ORA-06575: Package or function WWSBR_SITE_DB is in an
    ### 747 : 2020/28 PL/SQL: ORA-06575: Package or function WWSBR_SITE_DB is in an
    ### 751 : 2137/28 PL/SQL: ORA-06575: Package or function WWSBR_SITE_DB is in an
    ### 761 : 144/53     PL/SQL: ORA-06575: Package or function WWSBR_SITE_DB is in an
    ### 765 : 260/43     PL/SQL: ORA-06575: Package or function WWSBR_SITE_DB is in an
    ### 769 : 279/39     PL/SQL: ORA-06575: Package or function WWSBR_SITE_DB is in an
    ### 773 : 327/25     PL/SQL: ORA-06575: Package or function WWSBR_SITE_DB is in an
    ### 777 : 353/40     PLS-00905: object PORTAL.WWPOB_API_PAGE is invalid
    ### 779 : 369/42     PL/SQL: ORA-06575: Package or function WWPOB_API_PAGE is in an
    ### 783 : 376/48     PLS-00905: object PORTAL.WWPOB_API_PAGE is invalid
    ### 785 : 388/39     PL/SQL: ORA-06575: Package or function WWSBR_SITE_DB is in an
    ### 789 : 1216/42 PL/SQL: ORA-06575: Package or function WWSBR_SITE_DB is in an
    ### 793 : 1266/30 PL/SQL: ORA-06575: Package or function WWPOB_API_PAGE is in an
    ### 801 : 249/41     PL/SQL: ORA-06575: Package or function WWSBR_SITE_DB is in an
    ### 809 : 424/44     PL/SQL: ORA-06575: Package or function WWSBR_SITE_DB is in an
    ### 813 : 584/52     PLS-00905: object PORTAL.WWSBR_SITE_DB is invalid
    ### 819 : 2130/13 PLS-00905: object PORTAL.WWSBR_THING_TYPES is invalid
    ### 821 : 2132/13 PLS-00905: object PORTAL.WWSBR_THING_TYPES is invalid
    ### 823 : 2134/13 PLS-00905: object PORTAL.WWSBR_THING_TYPES is invalid
    ### 825 : 2136/13 PLS-00905: object PORTAL.WWSBR_THING_TYPES is invalid
    ### 827 : 2138/13 PLS-00905: object PORTAL.WWSBR_THING_TYPES is invalid
    ### 829 : 2140/13 PLS-00905: object PORTAL.WWSBR_THING_TYPES is invalid
    ### 831 : 2151/42 PLS-00320: the declaration of the type of this expression is
    ### 835 : 2152/42 PLS-00320: the declaration of the type of this expression is
    ### 839 : 2153/42 PLS-00320: the declaration of the type of this expression is
    ### 843 : 2212/27 PL/SQL: ORA-06575: Package or function WWSBR_THING_TYPES is in an
    ### 851 : 338/30     PL/SQL: ORA-06575: Package or function WWPOB_API_PAGE is in an
    ### 859 : 163/36     PL/SQL: ORA-06575: Package or function WWSBR_SITE_DB is in an
    ### 863 : 178/36     PL/SQL: ORA-06575: Package or function WWSBR_SITE_DB is in an
    ### 867 : 467/31     PL/SQL: ORA-06575: Package or function WWSBR_SITEBUILDER_PROVIDER
    ### 871 : 584/21     PL/SQL: ORA-06575: Package or function WWSBR_SITEBUILDER_PROVIDER
    ### 875 : 591/29     PL/SQL: ORA-06575: Package or function WWSBR_SITEBUILDER_PROVIDER
    ### 883 : 341/45     PLS-00302: component 'URL' must be declared
    ### 885 : 559/17     PLS-00320: the declaration of the type of this expression is
    ### 889 : 564/40     PLS-00320: the declaration of the type of this expression is
    ### 904 : ERROR at line 1:
    ### 905 : ORA-20000:
    ### 906 : ORA-06512: at "PORTAL.WWPOF", line 440
    ### 907 : ORA-06512: at line 45
    ### 908 : ORA-20000:
    ### 909 : ORA-06512: at "PORTAL.WWPOF", line 440
    ### 910 : ORA-06512: at "PORTAL.WWUTL_SCHEMA_VALIDATION", line 263
    ### 911 : ORA-04063: package body "PORTAL.WWUTL_PAGE_GROUP_VALIDATION" has errors
    ### 912 : ORA-06508: PL/SQL: could not find program unit being called
    ### 922 : # ERROR: When executing schema validation utility
    ### 923 : # ERROR: ORA-06508: PL/SQL: could not find program unit being called
    ### 933 : # ERROR: When running the schema validation utility
    ### 934 : # ERROR: ORA-20000:
    ### 935 : ORA-06512: at "PORTAL.WWPOF", line 440
    ### 936 : ORA-06512: at "PORTAL.WWUTL_SCHEMA_VALIDATION", line 263
    ### 937 : ORA-04063: package body "PORTAL.WWUTL_PAGE_GROUP_VALIDATION" has errors
    ### 938 : ORA-06508: PL/SQL: could not find program unit being called
    ### 947 : ### ERROR: Exception Executing upg/common/prechk/../../frwk/svurun.sql REPORT PRECHK for Subscriber: 1
    ### Check Failed at Wed Oct 18 21:22:32 2006 Continuing as PreCheck mode is specified
    Pre-Check Completed at Wed Oct 18 21:22:32 2006

    Hi,
    Its good that u pasted the complete log file. In your environment you have to run this upgrade tool only once from any of the middle tier.
    And with respect to your error that u got in precheck is quite simple. All u have to do is just run this script from by connecting to portal schema using sqlplus.
    Run dropupg.sql
    Location-------- /raid/product/OraHome_1/upgrade/temp/portal/prechktmp/dropupg.sql
    Later you re-run the upgrade tool and let me know the status.
    Good luck
    Tanmai

  • Help, need to change IP address on host database for Portal

    Hi folks,
    Rather urgent assistance (as usual) needed. I have an installation working correctly on a pair of Win2k machines, one as the 9i database, one as the 9iAS/Portal. The app server has 2 NIC cards, one with public IP address (which is ok), one on the LAN. I need to reconfigure the LAN addresses on both the machines. Initial Portal install done without DNS, i.e. actual server/host addresses entered in the configuration.
    I have tried changing all of the TNS/Listner settings and the NIC card IP addresses and restarting the machines. The likes of SQLPlus work ok, with the TNS connect name allowing over the LAN access into the database with the new LAN addresses. I cannot seem to get the 9iAS/Portal to find the repository with the new addresses.
    Can someone help please? I can't find the answer in any documentation or other postings.
    Thanks in advance
    Rob

    There are other modes of operation for the plasst as well. I am listing them below but the formatting will make it difficult to read. If you like I can email it to you.
    Bill G...
    Configuring Portal when the HTTP server host name of the Infrastructure is changed
    Run the following from the $ORACLE_HOME/assistants/opca dir
    ptlasst.bat -mode SSOPARTNERCONFIG -i typical -sdad portal -host myApache.domain.com -port 7777 -silent -verbose
    NOTE:
    (1) This command would create a new Portal partner application in the SSO to reflect the changes of the Infrastructure. Before running this command please ensure to configure the SSO with the correct hostname by running the ssocfg.bat script located in the Infrastructure install (<infra_home>\sso\bin).
    The value for -host parameter will be the IP address of the infrastructure server and -port will be the port where the infrastructure http server is running on.
    Configuring Portal when the HTTP server host name of the Middle tier is changed
    ptlasst.bat -mode MIDTIER -i typical -host myApache.domain.com -port 7777 -ldap_h myOID.domain.com -ldap_p 389 -ldap_w welcome -pwd secret123 -portal_only -oh /home/oracle -chost myHostname.domain.com -cport_i 8001 -cport_a 8000 -wc_i_pwd invalidator -mc false -mi true -silent -verbose
    NOTE :
    (1) The -host value should match the serverName value of the httpd.conf
    (2) The -chost should be updated with the correct webcache hostname. In a default iAS midtier install the -host is same as the -chost.
    The value for -host parameter will be the IP address of the midtier(portal) server and -port will be the port where the portal is running on.
    Parameter Description Default Value Mandatory
    -i install_type Installation Type
    In the typical mode, the OPCA would get the Infrastructure information like the Portal schema name, Portal schema password, connect string to the Portal repository, SSO Partner application schema and password, SSO Password store schema and password and connect string to the SSO repository from the Repository Access API's.
    In the custom mode, the OPCA would take whatever is passed as the command line arguments.
    CUSTOM
    -mode mode The different install modes are : PORTAL, SSO, SSOPARTNERCONFIG, LANGUAGE, MIDTIER, ALL, SYSOBJECTS , DEINSTALL
    -s portal_schema Oracle Database schema for Portal database objects. In an iAS 9.0.2 install
    the default Portal schema name is portal portal
    -sp portal_password Password for Portal schema. In an iAS 9.0.2 install the portal schema password is randomized by default. Refer to the note "How to get the Portal schema password of the Infrastructure database ?" for details. <portal_schema>
    -c portal_connect Connect string to connect to the Portal repository <hostname>:<port>:<sid>
    -p sys_password The Oracle Database password for the Oracle SYS user MANDATORY
    -sdad portal_dad DAD for the Portal schema. Create the DAD to the Portal repository through the OEM. Refer to the note "How to create and manage the Portal and SSO DAD ?" for details. <portal_schema>
    -host portal_host Hostname of the HTTP server for Portal. This should match byte to byte with whatever is present in the ServerName attribute in the $OH/Apache/Apache/conf/httpd.conf file of the midtier. MANDATORY
    -port portal_port Port of the HTTP server for Portal. The Port attribute in the $OH/Apache/Apache/conf/httpd.conf file of the midtier would provide the value. 7777
    -ldap_h oid_host_name Host name of the OID server MANDATORY
    -ldap_p oid_port_number Port number of the OID server 389
    -ldap_d oid_admin_DN Admininstration DN cn=orcladmin
    -ldap_w oid_admin_pw Password for DN welcome
    -pwd initial_password Initial Password for seeded OID users. In iAS 9.0.2 install this is defaulted to the iAS instance password of the midtier installation. MANDATORY (for ALL or MIDTIER)
    -das_public Add Portal Groups to DAS Public Groups. The values could be Y or N. The default is Y. The setting publishes the Portal groups that the user can add to when creating the new user in OID. Y
    -u default_tablespace Install Portal objects in this tablespace. The default tablespace selected should have atleast 75 MB of free available space and should have autoextend on. Refer to the note "What are the recommended tablespace size required for Portal installation ?" for details. The default tablespace selected by default is users tablespace. users
    -t temporary_tablespace Use this tablespace for temporary objects. The temporary tablespace selected should have atleast 20 MB of free available space and should have autoextend on. Refer to the note "What are the recommended tablespace size required for Portal installation ?" for details. The temporary tablespace selected by default is temp tablespace. temp
    -d document_tablespace Install Portal document table in this tablespace. The document tablespace selected should have atleast 4 MB of free available space and should have autoextend on. Refer to the note
    "What are the recommended tablespace size required for Portal installation ?" for details. The documented tablespace selected by default is users tablespace. <default_tablespace>
    -l logging_tablespace Install Portal logging tables in this tablespace. The Logging tablespace selected should have atleast 4 MB of free available space and should have autoextend on. Refer to the note "What are the recommended tablespace size required for Portal installation ?" for details. The Logging tablespace selected by default is users tablespace. <default_tablespace>
    -in index_tablespace Install Portal index in this tablespace. The Index tablespace selected should have atleast 20 MB of free available space and should have autoextend on. Refer to the note "What are the recommended tablespace size required for Portal installation ?" for details. The Index tablespace selected by default is users tablespace. <default_tablespace>
    -lang language Abbreviation for the language to install us
    -m language_mode Specifies the mode for language installation
    if sso, translations only for Login server.
    if portal, translations only for Portal.
    if -m not specified, translations are installed for Both
    -demo Install Portal webview demos
    -silent Run mode for Portal Configuration Assistant. There is no UI provided by OPCA in the iAS 9.0.2 install. Use -silent option always
    -verbose Log mode for Portal Configuration Assistant. If this parameter is not set, logging information would be in brief and the OPCA would abort the install if it encounters any errors of kind
    ORA-, PLS- or SP2 errors.
    -report Install reports integration with Portal
    -owa Install OWA packages along with Portal This option behaves the same as the SYSOBJECTS mode.
    -sso_only Configure only SSO in mid-tier mode
    -portal_only Configure only Portal in mid-tier mode
    -available Language will be available for user translation
    -chost cache_host Cache host for Web Cache <hostname>
    -cport_i cache_inv_port Cahe port for Web Cache Invalidation 1100
    -cport_a cache_adm_port Cahe port for Web Cache Administration 1000
    -wc_i_pwd wc_inv_passwd Web Cache invalidator password invalidator
    -wc wc_on_off_flag Web Cache ON/OFF flag to enable or disable WC. The default is ON. If set to OFF Portal would not use Webcache though Web Cache may be up and running. on
    -o sso_schema Oracle Database schema for Login Server objects. In an iAS 9.0.2 install the default SSO schema name is orasso orasso
    -op sso_password Password for Login Server Schema. In an iAS 9.0.2 install the SSO schema password is randomized by default. Refer to the note "How to get the Portal schema password of the Infrastructure database ?" for more details. Use similar steps to get the password of the orasso. MANDATORY for the following modes:
    -MIDTIER: except when '-portal_only' is specified
    -LANGUAGE: except when '-m portal' is specified
    -DEINSTALL: except when '-drop PORTAL' is specified
    -odad sso_dad DAD for Login Server objects. Create the DAD to the SSO repository through the OEM. Refer to the note "How to create and manage the Portal and SSO DAD ?" for details. <sso_schema>
    -sso_c sso_connect Connect string to connect to the SSO repository If the Portal and SSO use the same database this option need not be passed and would default to the -c argument. <hostname>:<port>:<sid>
    -sso_h sso_host Hostname of the HTTP server for the SSO. If Portal and SSO use the same HTTP server this option need not be passed. It would default the HTTP server used for the Portal.
    -sso_p sso_port Port of the HTTP server for the SSO. If Portal and SSO use the same HTTP server this option need not be passed. It would default the HTTP port used for the Portal.
    -pa papp_schema SSO Partner Application Registration Schema. In an iAS 9.0.2 install the default Password store schema name is orasso_pa <sso_schema>_PA  
    -pap papp_password SSO PA Schema Password. In an iAS 9.0.2 install the SSO schema password is randomized by default. Refer to the note "How to get the Portal schema password of the Infrastructure database ?" for more details. Use similar steps to get the password of the orasso_pa <papp_schema>
    -ps pstore_schema Password Store Schema. In an iAS 9.0.2 install the default Password store schema name is orasso_ps <sso_schema>_PS  
    -pp pstore_password Password Store Password. In an iAS 9.0.2 install the SSO schema password is randomized by default. Refer to the note "How to get the Portal schema password of the Infrastructure database ?" for more details. Use similar steps to get the password of the orasso_ps. <ptore_schema>
    -pd pstore_dblink Database link from Portal schema to Password store. If the Portal and SSO use the same database this option need not be passed. <portal_schema>_DBLINK  
    -p_tns pstore_tns TNS connect string to Password Store. If the Portal and SSO use the same database this option need not be passed. The tnsalias should be created in the iAS 9.0.2 Portal middle tier.
    -s_tns portal_tns TNS connect string to Portal
    -ssotype ssotype SSO install type. Valid values are repository, midtier, all Repository
    -ultrasearch Ultrasearch configuration
    -drop drop_obj Drops either PORTAL or SSO or ALL (Both)
    if PORTAL, drops Portal schema and OID entries.
    if SSO,drops Portal schema and OID entries.
    if ALL, drops Portal and SSO schema and OID entries
    -oh oracle_home Oracle Home
    -mi midtier_install Midtier Installation
    -mc midtier_config Midtier Configuration
    -ssl Use SSL protocol for configuration. Pass this parameter only if SSL configuration is required. If this parameter is passed the -port passed should also be the SSL port of the HTTP server. Bt default this is not passed.
    -emhost em_host Enterprise Manager host for monitoring <hostname>
    -emport em_port Enterprise Manager port for monitoring 1810
    -iasname ias_name Name of the iAS instance that the install is installing on

  • EXTREMELY URGENT - Ultrasearch integration with portal giving errors

    gurus,
    i'm creating a portal source for Ultrasearch and when i register the portal site with Ultrasearch i get the following error -
    ----- START ERROR -------
    Oracle Ultra Search Error
    Could not retrieve data from Oracle 9iAS portal. Please make sure that the URL base is correct and that the portal is
    operational.
    ------ END ERROR -------
    i looked into the error.log file in $APACHE_HOME/Apache/logs and found the following in the error log file -
    http 404 - portal.home.wwsbr_srchxml.execute : Procedure does not exist
    can anyone explain what this means ....
    i looked for wwsbr_srchxml package and it is valid and owned by portal.
    ideas ...?
    any help will be greatly appreciated ....
    thanx

    Issue:
    Couldn't register the portal as a data source within the UltraSearch
    Resolution:
    When registering the portal URL Base it executes a procedure on the portal schema (using the part of the portal.home to execute the procedure)
    There for to register we have to use http://hostname:port/pls/portal/portal
    The last "portal" is whats used to execute the wwsbr_srchxml.execute procedure.
    The log in the Apache/Apache/logs/error_log...
    [Thu Jul 25 18:04:12 2002] [error] mod_plsql: /pls/portal/portal.home.wwsbr_srchxml.execute HTTP-404
    portal.home.wwsbr_srchxml.execute: PROCEDURE DOESN'T EXIST
    so basically its looking for portal.home.wwsbr_srchxml.execute which doesn't exist, since its inside the portal schema not the "portal.home" schema.
    Thanks,

  • EXTREMELY URGENT - Ultrasearch integration with oracle portal giving erros -

    gurus,
    i'm creating a portal source for Ultrasearch and when i register the portal site with Ultrasearch i get the following error -
    ----- START ERROR -------
    Oracle Ultra Search Error
    Could not retrieve data from Oracle 9iAS portal. Please make sure that the URL base is correct and that the portal is
    operational.
    ------ END ERROR -------
    i looked into the error.log file in $APACHE_HOME/Apache/logs and found the following in the error log file -
    http 404 - portal.home.wwsbr_srchxml.execute : Procedure does not exist
    can anyone explain what this means ....
    i looked for wwsbr_srchxml package and it is valid and owned by portal.
    ideas ...?
    any help will be greatly appreciated ....
    thanx

    Issue:
    Couldn't register the portal as a data source within the UltraSearch
    Resolution:
    When registering the portal URL Base it executes a procedure on the portal schema (using the part of the portal.home to execute the procedure)
    There for to register we have to use http://hostname:port/pls/portal/portal
    The last "portal" is whats used to execute the wwsbr_srchxml.execute procedure.
    The log in the Apache/Apache/logs/error_log...
    [Thu Jul 25 18:04:12 2002] [error] mod_plsql: /pls/portal/portal.home.wwsbr_srchxml.execute HTTP-404
    portal.home.wwsbr_srchxml.execute: PROCEDURE DOESN'T EXIST
    so basically its looking for portal.home.wwsbr_srchxml.execute which doesn't exist, since its inside the portal schema not the "portal.home" schema.
    Thanks,

  • Creating users using custom made class/UI in portal

    This is what i have to achieve,
    I need to create an interface in portal which will,
    1. Create users in the OID where the users extend a class which i have created in OID with my custom attributes.
    2. Then create them in portal and then assign them to default groups which will depend on a parameter in the user creation form.
    From reading various documents in Metalink and OTN i have understood that the wwsec_api package allows us to do all this except that it is all for a user which will extend a predefined set of classes.
    So i decided to do this
    1.Make entries into the OID using the DBMS_LDAP package using commands like
    emp_vals(1) := p_first_name;
    DBMS_LDAP.populate_mod_array(emp_array,DBMS_LDAP.MOD_ADD,'firstName',emp_vals);
    retval := DBMS_LDAP.add_s(emp_session,emp_dn,emp_array);
    2.Fire the wwsec_api.add_portal_user to create the portal user and then activate and assign him to the default group after running the provsyns.sql file
    The problem i face is that i get errors when i execute the said procedure from any other schema other than portal.
    When the procedure is recreated in the portal schema and executed it works fine.
    So i decided to create the entire package in the portal schema itself.
    Now the problem i face is that the proc would execute fine on the sql prompt but fail when called from the form created in portal based on this procedure.
    I found out that the execution fails when the wwsec_api.xxx calls are made.
    The exceptions are not specific and have the error code 1 => user defined exception
    To have a workaround for this i directly inserted into the wwsec_person$ table with no values for the GUID column( I know this is not recommended but i gave it a try)
    The insert worked fine but i still had to set his default group.I tried updating the rows for the user to set the default_group column but there seems to be a trigger on it which causes the update to fail.
    Also when i check up the wwsec_person$ table there two rows for each user that i created ,one without the GUID/default_group and the other with the GUID/default_group.I guess this is because of the trigger.
    If i try using the wwsec_api.set_defaultgroup api, the proc fails.
    It is quite interesting to note that all the steps mentioned above, grant access to the user to portal.
    But the place it fails is while setting the default group for the same which is of prime importance to me.
    Also because I am inserting directly into the tables i have also to delete them when the user is deleted, this is because i again cannot execute the delete_portal_user in the wwsec_api package from the browser.
    Surprisingly the wwsec_api.create_list function works fine.
    Once i have created the users all the manipulations like changing group memberships etc become easy as i just modify the required details in the OID itself.
    What i need is a proper/safe way to do what i have just mentioned above.
    Please help out ASAP as this is urgent.
    Regards,
    KK

    Based on your requirements, you should go about things a little differently...
    You have written your custom DBMS_LDAP code to create and populate the user entry including your custom objectclasses - good.
    You don't need to create the user profile in the Portal schema at all.
    To set the default group, just set the orcldefaultprofilegroup attribute in the user entry in OID. This should be set to the DN of the default group.
    When the user logs on, his profile will automatically be created, and the default group will also sync up with the user entry in OID (patch required - 2830252).
    Also, you should have DIP provisioning running so that updates to the orcldefaultprofilegroup attribute in OID are subsequently conveyed to the portal schema. It will also take care of automatically deleting the user profile from the portal if the user is removed from OID.
    Please see the Portal Configuration Guide on how to enable and activate the Directory Integration Platform (DIP) provisioning integration between OID and Portal

  • Portal Repository

    Hello All.
    What is the Portal Repository? Do I need a new database to store it or can I put in already exist database.

    Hi -
    The Portal repository is the schema owned by Portal that contains all the tables and API's used within Portal. Everything produced by Portal is essentially generated dynamically from the database using the programs and data in its repository, and is displayed in a web browser.
    You can store it in an existing database (that is the easy answer) but there is quite a bit to it. There needs to be 3 separate physical (or logical) servers - one for the database and portal repository, one for the infrastructure database (including Oracle Internet Directory) and one for the web (application) server. Portal is just one aspect of 9iAS. I've never done the install but it is very difficult with many pitfalls. Read all the release notes and have your ducks in a row before you start.
    Art

  • Export /Import of Portal -Urgent -Attn Product Mgr Group

    I m planning to move my current portal database to other box (Win2000-> HP)and keeping apache and portal tec stack on current box.
    Which of following method is safe and tested.
    1. Export whole data base (8.1.7.3) and import it as a full data base on target box.
    2.Or export it user wise.All users ,specially portal%.
    Please advice how to clone or migrate from deployement to test server.Different documentaion says different things.In document named "Import export in portal', they say portal30 can not be exported.While in Document "Migration of Portal Across Datbases" they suggested to export all schemas related to portal.In portal forum some users mentioned that they migrated from deployment to test/development using full database export ,saying that oracle suggests this, but there is no recovery method for it.
    My second objective is to seprate apache from database.Keeping existing apache on NT box (current instance) and data(portal schemas) on HP box.
    Is there any thing else to be done except modifying DAD on current apache.
    Thanks
    Sarvesh

    You can do the following to export your portal objects alone (I am talking wrt 30982) . Do it in that order please.
    1. Go to the WWU directory where you will find the scripts related to export/import.
    2. First run the SSOEXP utility for exporting all the users and groups. (The result is a dump say sso.dmp)
    2. Next, run the SECEXP utility for exporting all the previliges of all the users on different objects. (The result is sec.dmp)
    3. Then run the APPEXP utility for exporting your applications, you could give the "-security" option here as well (The result is app.dmp)
    4. Run the PAGEEXP utility for exporting your pages (This gives pages.dmp).
    5. Lastly run the CONTEXP utility for exporting your content areas (This results in contarea.dmp)
    These five dumps can be supplied to the corresponding import utilities for importing your stuff.
    But, if you are planning to export/import the entire database, then please enquire with the RDBMS migration experts about this.
    Hope this helps.

Maybe you are looking for

  • Mview fast refresh taking longer than complete refresh

    Hi there, We have a mview which takes about an hour to refresh in complete mode. Created all the mview logs and refreshing via fast method but this takes longer. When all the mview logs empty works fine as fast refresh and far far quicker as would ex

  • HT4848 what recovery assistant is recommended for the intel core 2 duo 2gb macbook?

    After sending a flashdrives contents to the waste basket and emptying it, for some reason the file on the desktop containing identical files lost part of its content. Can I recover either the flash drive or the contents of the folder using some recov

  • Safari quits only on one Discussions forum

    I have a weird thing happening. When I go to my bookmark for Apples Logic Pro discussions forum, Safari immediately quits. This also happens when I navigate there from Apples home page, so I don't think it's bookmark related... I can get to any other

  • Sap Script printing issue

    Hi Gurus, I am working on a SAP script... when I am printing the SAP script the last few lines of my text is missing... I got to know that there might be a problem in the page setting... i.e. the page may be set as a A4 and i am printing on letter...

  • Error code -36 when emptying trash...Please Help !!!!!!

    Hey there, im having problems emptying the trash on my macbookpro and I wonder is it the problem that slows down my computer too because it has been awhile since i have emptied my trash and now I can't empty it due to the error showed as "PodcastsPla