Error: The preference path does not exist

Question

Subject:
Error: The preference path does not exist:
Oracle.Portal.Page(WWC-51000)]
I can not resolve this error.
Have you already experienced this error?
I'm sending more information below.
Regards, Dime
DETAILS:
========
ORACLE Product: iAS 9i EE, v1.0.2
Platform: RedHat Linox 6.2, kernel 2.2.18
HW Platform:
IBM Intellistation 6889, Intel P2 350MHz, 384MB
Problem:
After successful installation of the Application Server and data base creation, the installation of ORACLE Portal 3.0.6 is successful too, but the following message
appears when we try to access the URL http://servername:port/pls/portal30:
Error: The preference path does not exist:
Oracle.Portal.Page (WWC-51000)
About the Attachments:
- init.ora.original (the original init.ora file)
- init.ora.try1 (the file modified as described in the configuration guide)
- init.ora.try2 (according suggestions in the discussion group on
the ORACLE Metal Partners Site)
- install.log (install.log generated with init.ora.try2)
Regards,
Dimitar Indovski,
GORD Systems
ATTACHMENT-1 (init.ora.original)
db_name=DEFAULT
db_files= 80 # SMALL
db_file_multiblock_read_count = 8 # SMALL
db_block_buffers = 100 # SMALL
shared_pool_size = 3500000 # SMALL
log_checkpoint_interval = 10000
processes = 50 # SMALL
parallel_max_servers = 5 # SMALL
log_buffer = 32768 # SMALL
max_dump_file_size = 10240 # limit trace file size to 5 Meg each
global_names = TRUE
control_files = (ora_control1, ora_control2)
ATTACHMENT-2 (init.ora.try1)
db_name=DEFAULT
db_files = 80 # SMALL
db_file_multiblock_read_count = 8 # SMALL
db_block_buffers = 100 # SMALL
shared_pool_size = 3500000 # SMALL
log_checkpoint_interval = 10000
processes = 50 # SMALL
parallel_max_servers = 5 # SMALL
log_buffer = 32768 # SMALL
max_dump_file_size = 10240 # limit trace file size to 5 Meg each
global_names = TRUE
control_files = (ora_control1, ora_control2)
max_enabled_roles = 25
open_cursors = 50
compatible = 8.1.0
java_pool_size = 20
ATTACHMENT-3 (init.ora.try2)
db_name=DEFAULT
db_file_multiblock_read_count = 16
db_block_buffers = 550
shared_pool_size = 31457280
log_checkpoint_interval = 10000
processes = 100
parallel_max_servers = 5
log_buffer = 32768
max_dump_file_size = 10240
global_names = TRUE
control_files = (ora_control1, ora_control2)
open_cursors = 300
large_pool_size = 45000000
java_pool_size = 32768000
db_block_size = 8192
ATTACHMENT-4 (install.log.gz)
-----------------------------

Answer 1

Dennis
A general shared_pool_size Q&A is part of the Troubleshooting Guide on OTN: http://technet.oracle.com/products/iportal/htdocs/portal_troubleshooting.htm
The Configuration Assistant determines the shared pool size from the view v$parameter,
which lists information about the initialization parameters (populated from init.ora file). If the shared_pool_size value is more than 15728640 (for a default installation), you pass the minimal requirements set by the Portal Installer. Make sure you actually write out all the digits (i.e. 1000000000) and don't use abbreviations (1000M). Currently, the Configuration Assistant does a numeric check against the values that are set and cannot resolve the abbreviate syntax.
Also try running the sql [select value from v$parameter where name like 'shared_pool_size';] to check if the changes you are making in the init.ora is really getting populated in the v$parameter view. As long as you restart the database once you make the change in init.ora, it should take effect.
null