VMS port of BerkeleyDB

Hi,
I am wondering if you can help me with a little archaeology expedition.
I understand from the Change Log for Berkeley DB, that very early versions (i.e. up to V2.7.7) were available to be compiled on a VMS platform. If it is still possible to obtain the instructions to build the OpenVMS Alpha of Berkeley DB, this would be of immense interest to me. I've tried to apply the generic /PORT build instructions described in V1.8.5 and apply them to V1.8.5 and V2.7.7, but the builds fails, possibly due to symbolic link differences (I used VMS logicals and symbols to substitute for Unix's ln -s command) but even putting all the files in /include, etc., it still didn't compile/build. I am getting the distinct feeling that I did not grasp the full build process correct to be able to adapt it to a VMS environment.
The underlying situation is that I have Perl 5.8.6 and am migrating a Perl application from its current incarnation to this. In addition, I would like to take the opportunity to upgrade the DBM modules that it accesses to DB_File (which is the Perl interface to Berkeley DB, via yet another interface known as AnyDBM_File).
If anyone would be able to point to instructions to build Berkeley on OpenVMS Alpha 7.3-2 and specify what directory structure, source code modules, etc., that I need, it would be very beneficial experience and, hopefully (if literature is to be believed) provide good performance improvements too.
Yours gratefully,
Christopher

Hello,
One product you may want to look in to is GNV.
It is a layered product which can be installed on
some versions of VMS. It provides a Unix-like
environment with a bash shell and many utilities.
Some other information which may be useful to you is at:
http://www.oracle.com/technology/documentation/berkeley-db/db/ref/distrib/port.html
thanks,
Sandra

Similar Messages

Database Instance Installation Problem on Oracle 8.1.7

Dear gurus,
I'm having problem when installing Database Central Instance on Solaris 10 - Oracle 8.1.7 (32bit) - SAP 4.6c.
Here's the error log:
Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production
With the Partitioning option
JServer Release 8.1.7.0.0 - Production
Connected.
Echo                            ON
SVRMGR> SET TERMOUT ON;
Termout                         ON
SVRMGR> SHUTDOWN ABORT;
ORACLE instance shut down.
SVRMGR> STARTUP NOMOUNT PFILE=init.ora;
ORA-27123: unable to attach to shared memory segment
SVR4 Error: 22: Invalid argument
Additional information: 1
Additional information: 3
SVRMGR> CREATE DATABASE PRD
     2> CONTROLFILE REUSE
     3> MAXDATAFILES 254
     4> MAXLOGFILES   255
     5> MAXLOGHISTORY 1000
     6> MAXLOGMEMBERS 3
     7> MAXINSTANCES 50
     8> CHARACTER SET "WE8DEC"
     9> DATAFILE
    10> '/oracle/PRD/sapdata1/system_1/system.data1' SIZE 300M REUSE
    11> NOARCHIVELOG
Info: DBCREATEDB_IND_ORA SvrmgrDoDummy 2 349
    12> LOGFILE
    13> GROUP 11 (
    14> '/oracle/PRD/origlogA/log_g11m1.dbf',
    15> '/oracle/PRD/mirrlogA/log_g11m2.dbf'
    16> ) SIZE 20M REUSE
    17> ,GROUP 13 (
    18> '/oracle/PRD/origlogA/log_g13m1.dbf',
    19> '/oracle/PRD/mirrlogA/log_g13m2.dbf'
    20> ) SIZE 20M REUSE
    21> ,GROUP 12 (
    22> '/oracle/PRD/origlogB/log_g12m1.dbf',
    23> '/oracle/PRD/mirrlogB/log_g12m2.dbf'
    24> ) SIZE 20M REUSE
    25> ,GROUP 14 (
    26> '/oracle/PRD/origlogB/log_g14m1.dbf',
    27> '/oracle/PRD/mirrlogB/log_g14m2.dbf'
    28> ) SIZE 20M REUSE
    29> ;
CREATE DATABASE PRD
ORA-01034: ORACLE not available
SVRMGR> EXIT
Server Manager complete.
Error: DBCREATEDB_IND_ORA InternalInstallationDo 2 349
Create Database failed errorcode = 27123.
Error: DBCREATEDB_IND_ORA InstallationDo 2 349
Phase failed.
Error: Main {} 2 349
Installation aborted.
I have tweaked the shared memory max as suggested in Oracle Manual / SAP Installation Guide, to no avail.
The listener is up already.
When I logged in as user ORA<SID>, and go to svrmgrl > startup nomount pfile=init.ora, it can startup without hassle.
Although the Product is not supported in PAM, we have another machine running smoothly for years with this product combination, so it's not the product compatibility issues.
But when using R3SETUP -f DATABASE.R3S, the phase stopped with the log pasted above.
Any ideas, gurus?
Thanks for help.
Best Regards,

Mr. Markus, there's no file on saptrace/usertrace.
To be sure, here's what I've done:
1. Run oracle listener.
2. Check connection with svrmgrl > connect internal (connected).
3. Modify init.ora with my DB Name:
wef
# replace DEFAULT with your database name
*db_name=PRDDB*
db_files = 80                                                         # SMALL
# db_files = 400                                                      # MEDIUM
# db_files = 1500                                                     # LARGE
db_file_multiblock_read_count = 8                                     # SMALL
# db_file_multiblock_read_count = 16                                  # MEDIUM
# db_file_multiblock_read_count = 32                                  # LARGE
db_block_buffers = 100                                                 # SMALL
# db_block_buffers = 550                                              # MEDIUM
# db_block_buffers = 3200                                             # LARGE
shared_pool_size = 3500000                                            # SMALL
# shared_pool_size = 5000000                                          # MEDIUM
# shared_pool_size = 9000000                                          # LARGE
log_checkpoint_interval = 10000
processes = 50                                                        # SMALL
# processes = 100                                                     # MEDIUM
# processes = 200                                                     # LARGE
parallel_max_servers = 5                                              # SMALL
# parallel_max_servers = 4 x (number of CPUs)                         # MEDIUM
# parallel_max_servers = 4 x (number of CPUs)                         # LARGE
log_buffer = 32768                                                    # SMALL
# log_buffer = 32768                                                  # MEDIUM
# log_buffer = 163840                                                 # LARGE
# audit_trail = true            # if you want auditing
# timed_statistics = true       # if you want timed statistics
max_dump_file_size = 10240      # limit trace file size to 5 Meg each
# Uncommenting the line below will cause automatic archiving if archiving has
# been enabled using ALTER DATABASE ARCHIVELOG.
# log_archive_start = true
# log_archive_dest = disk$rdbms:[oracle.archive]
# log_archive_format = "T%TS%S.ARC"
# If using private rollback segments, place lines of the following
# form in each of your instance-specific init.ora files:
# rollback_segments = (name1, name2)
# If using public rollback segments, define how many
# rollback segments each instance will pick up, using the formula
#   # of rollback segments = transactions / transactions_per_rollback_segment
# In this example each instance will grab 40/5 = 8:
# transactions = 40
# transactions_per_rollback_segment = 5
# Global Naming -- enforce that a dblink has same name as the db it connects to
global_names = TRUE
# Edit and uncomment the following line to provide the suffix that will be
# appended to the db_name parameter (separated with a dot) and stored as the
# global database name when a database is created. If your site uses
# Internet Domain names for e-mail, then the part of your e-mail address after
# the '@' is a good candidate for this parameter value.
# db_domain = us.acme.com       # global database name is db_name.db_domain
# FOR DEVELOPMENT ONLY, ALWAYS TRY TO USE SYSTEM BACKING STORE
# vms_sga_use_gblpagfil = TRUE
# FOR BETA RELEASE ONLY. Enable debugging modes. Note that these can
# adversely affect performance. On some non-VMS ports the db_block_cache_*
# debugging modes have a severe effect on performance.
#_db_block_cache_protect = true                       # memory protect buffers
#event = "10210 trace name context forever, level 2" # data block checking
#event = "10211 trace name context forever, level 2" # index block checking
#event = "10235 trace name context forever, level 1" # memory heap checking
#event = "10049 trace name context forever, level 2" # memory protect cursors
# define parallel server (multi-instance) parameters
#ifile = ora_system:initps.ora
# define two control files by default
control_files = (ora_control1, ora_control2)
# Uncomment the following line if you wish to enable the Oracle Trace product
# to trace server activity. This enables scheduling of server collections
# from the Oracle Enterprise Manager Console.
# Also, if the oracle_trace_collection_name parameter is non-null,
# every session will write to the named collection, as well as enabling you
# to schedule future collections from the console.
# oracle_trace_enable = TRUE
# Uncomment the following line, if you want to use some of the new 8.1
# features. Please remember that using them may require some downgrade
# actions if you later decide to move back to 8.0.
#compatible = 8.1.0
3. set shared memory parameter as in sapnote 724713.
4. executing R3SETUP
and it tells me this error:
Info: DBCREATEROLLSEGSTART_IND_ORA SyGroupIDGet 2 354
Group id for group dba is 102.
Info: DBCREATEROLLSEGSTART_IND_ORA SyUserIDGet 2 354
User id for user oraprd is 100.
Info: DBCREATEROLLSEGSTART_IND_ORA SvrmgrDoDummy 2 354
Return from DB: 1034.
Info: DBCREATEROLLSEGSTART_IND_ORA SvrmgrDoDummy 2 354
Oracle Server Manager Release 3.1.7.0.0 - Production
Copyright (c) 1997, 1999, Oracle Corporation. All Rights Reserved.
Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production
With the Partitioning option
JServer Release 8.1.7.0.0 - Production
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
SVR4 Error: 2: No such file or directory
Server Manager complete.
Info: DBCREATEROLLSEGSTART_IND_ORA InternalInstallationDo 2 354
Startup Database.
Info: DBCREATEROLLSEGSTART_IND_ORA OracleCmd 2 354
Startup Database with PFILE: init.ora.
Info: DBCREATEROLLSEGSTART_IND_ORA SyCoprocessCreateAsUser 2 354
Creating coprocess /oracle/PRD/817_32/bin/svrmgrl [email protected] as user oraprd and group dba ...
Info: DBCREATEROLLSEGSTART_IND_ORA SyGroupIDGet 2 354
Group id for group dba is 102.
Info: DBCREATEROLLSEGSTART_IND_ORA SyUserIDGet 2 354
User id for user oraprd is 100.
Info: DBCREATEROLLSEGSTART_IND_ORA SvrmgrDoDummy 2 354
Return from DB: 27123.
Info: DBCREATEROLLSEGSTART_IND_ORA SvrmgrDoDummy 2 354
Oracle Server Manager Release 3.1.7.0.0 - Production
Copyright (c) 1997, 1999, Oracle Corporation. All Rights Reserved.
Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production
With the Partitioning option
JServer Release 8.1.7.0.0 - Production
Connected.
ORA-27123: unable to attach to shared memory segment
SVR4 Error: 22: Invalid argument
Additional information: 1
Additional information: 2
alter database noarchivelog
ORA-01034: ORACLE not available
alter database open
ORA-01034: ORACLE not available
Server Manager complete.
Error: DBCREATEROLLSEGSTART_IND_ORA InternalInstallationDo 2 354
Startup Database with error: 27123.
Error: DBCREATEROLLSEGSTART_IND_ORA InstallationDo 2 354
Phase failed.
Error: Main {} 2 354
Installation aborted.
It's driving me nuts for the last days.. can't figure out what happened here.

Unable to find the utl_file_directory option in init.ora

Hi all these are the contents of init.ora file in nacedell server.i did'nt find any thing as utl_file_directory to update with my directory created through sql*plus using
command
create directory dir as 'c:\dir';
here are the contents of init.ora file
cat init.ora command is giving contents as
# $Header: init.ora 06-aug-98.10:24:40 atsukerm Exp $
# Copyright (c) 1991, 1997, 1998 by Oracle Corporation
# NAME
# init.ora
# FUNCTION
# NOTES
# MODIFIED
# atsukerm 08/06/98 - fix for 8.1.
# hpiao 06/05/97 - fix for 803
# glavash 05/12/97 - add oracle_trace_enable comment
# hpiao 04/22/97 - remove ifile=, events=, etc.
# alingelb 09/19/94 - remove vms-specific stuff
# dpawson 07/07/93 - add more comments regarded archive start
# maporter 10/29/92 - Add vms_sga_use_gblpagfile=TRUE
# jloaiza 03/07/92 - change ALPHA to BETA
# danderso 02/26/92 - change db_block_cache_protect to dbblock_cache_p
# ghallmar 02/03/92 - db_directory -> db_domain
# maporter 01/12/92 - merge changes from branch 1.8.308.1
# maporter 12/21/91 - bug 76493: Add control_files parameter
# wbridge 12/03/91 - use of %c in archive format is discouraged
# ghallmar 12/02/91 - add global_names=true, db_directory=us.acme.com
# thayes 11/27/91 - Change default for cache_clone
# jloaiza 08/13/91 - merge changes from branch 1.7.100.1
# jloaiza 07/31/91 - add debug stuff
# rlim 04/29/91 - removal of char_is_varchar2
# Bridge 03/12/91 - log_allocation no longer exists
# Wijaya 02/05/91 - remove obsolete parameters
# Example INIT.ORA file
# This file is provided by Oracle Corporation to help you customize
# your RDBMS installation for your site. Important system parameters
# are discussed, and example settings given.
# Some parameter settings are generic to any size installation.
# For parameters that require different values in different size
# installations, three scenarios have been provided: SMALL, MEDIUM
# and LARGE. Any parameter that needs to be tuned according to
# installation size will have three settings, each one commented
# according to installation size.
# Use the following table to approximate the SGA size needed for the
# three scenarious provided in this file:
# -------Installation/Database Size------
# SMALL MEDIUM LARGE
# Block 2K 4500K 6800K 17000K
# Size 4K 5500K 8800K 21000K
# To set up a database that multiple instances will be using, place
# all instance-specific parameters in one file, and then have all
# of these files point to a master file using the IFILE command.
# This way, when you change a public
# parameter, it will automatically change on all instances. This is
# necessary, since all instances must run with the same value for many
# parameters. For example, if you choose to use private rollback segments,
# these must be specified in different files, but since all gc_*
# parameters must be the same on all instances, they should be in one file.
# INSTRUCTIONS: Edit this file and the other INIT files it calls for
# your site, either by using the values provided here or by providing
# your own. Then place an IFILE= line into each instance-specific
# INIT file that points at this file.
# NOTE: Parameter values suggested in this file are based on conservative
# estimates for computer memory availability. You should adjust values upward
# for modern machines.
# You may also consider using Database Configuration Assistant tool (DBCA)
# to create INIT file and to size your initial set of tablespaces based
# on the user input.
# replace DEFAULT with your database name
db_name=DEFAULT
db_files = 80 # SMALL
# db_files = 400 # MEDIUM
# db_files = 1500 # LARGE
db_file_multiblock_read_count = 8 # SMALL
# db_file_multiblock_read_count = 16 # MEDIUM
# db_file_multiblock_read_count = 32 # LARGE
db_block_buffers = 100 # SMALL
# db_block_buffers = 550 # MEDIUM
# db_block_buffers = 3200 # LARGE
shared_pool_size = 3500000 # SMALL
# shared_pool_size = 5000000 # MEDIUM
# shared_pool_size = 9000000 # LARGE
log_checkpoint_interval = 10000
processes = 50 # SMALL
# processes = 100 # MEDIUM
# processes = 200 # LARGE
parallel_max_servers = 5 # SMALL
# parallel_max_servers = 4 x (number of CPUs) # MEDIUM
# parallel_max_servers = 4 x (number of CPUs) # LARGE
log_buffer = 32768 # SMALL
# log_buffer = 32768 # MEDIUM
# log_buffer = 163840 # LARGE
# audit_trail = true # if you want auditing
# timed_statistics = true # if you want timed statistics
max_dump_file_size = 10240 # limit trace file size to 5 Meg each
# Uncommenting the line below will cause automatic archiving if archiving has
# been enabled using ALTER DATABASE ARCHIVELOG.
# log_archive_start = true
# log_archive_dest = disk$rdbms:[oracle.archive]
# log_archive_format = "T%TS%S.ARC"
# If using private rollback segments, place lines of the following
# form in each of your instance-specific init.ora files:
# rollback_segments = (name1, name2)
# If using public rollback segments, define how many
# rollback segments each instance will pick up, using the formula
# # of rollback segments = transactions / transactions_per_rollback_segment
# In this example each instance will grab 40/5 = 8:
# transactions = 40
# transactions_per_rollback_segment = 5
# Global Naming -- enforce that a dblink has same name as the db it connects to
global_names = TRUE
# Edit and uncomment the following line to provide the suffix that will be
# appended to the db_name parameter (separated with a dot) and stored as the
# global database name when a database is created. If your site uses
# Internet Domain names for e-mail, then the part of your e-mail address after
# the '@' is a good candidate for this parameter value.
# db_domain = us.acme.com # global database name is db_name.db_domain
# FOR DEVELOPMENT ONLY, ALWAYS TRY TO USE SYSTEM BACKING STORE
# vms_sga_use_gblpagfil = TRUE
# FOR BETA RELEASE ONLY. Enable debugging modes. Note that these can
# adversely affect performance. On some non-VMS ports the db_block_cache_*
# debugging modes have a severe effect on performance.
#_db_block_cache_protect = true # memory protect buffers
#event = "10210 trace name context forever, level 2" # data block checking
#event = "10211 trace name context forever, level 2" # index block checking
#event = "10235 trace name context forever, level 1" # memory heap checking
#event = "10049 trace name context forever, level 2" # memory protect cursors
# define parallel server (multi-instance) parameters
#ifile = ora_system:initps.ora
# define two control files by default
control_files = (ora_control1, ora_control2)
# Uncomment the following line if you wish to enable the Oracle Trace product
# to trace server activity. This enables scheduling of server collections
# from the Oracle Enterprise Manager Console.
# Also, if the oracle_trace_collection_name parameter is non-null,
# every session will write to the named collection, as well as enabling you
# to schedule future collections from the console.
# oracle_trace_enable = TRUE
# Uncomment the following line, if you want to use some of the new 8.1
# features. Please remember that using them may require some downgrade
# actions if you later decide to move back to 8.0.
#compatible = 8.1.0
$

There are strange things in the file you posted, are you sure that's your init.ora ? where did you find it ?
Moreover, you use "cat" to list the file, but you name "c:\dir" the directory : what is your OS ?
Furthermore, if you use directories, then you don't need to set utl_file_dir in init.ora, and directories don't show up within parameters, you can see them by
SQL> select * from all_directories;

Oracle not starting up throwing error

My listener problem is solved but the DB dosent start up and throws this error, I also have a dump of the startup.log and the copy of init.ora file.
[oracle@localhost ~]$ ./oracle.sh start
Starting Oracle: Password:
LSNRCTL for Linux: Version 10.2.0.1.0 - Production on 24-DEC-2009 23:01:32
Copyright (c) 1991, 2005, Oracle. All rights reserved.
TNS-01106: Listener using listener name LISTENER has already been started
Password:
Failed to auto-start Oracle Net Listene using /ade/vikrkuma_new/oracle/bin/tnslsnr
Processing Database instance "sales": log file /u01/app/oracle/oracle/product/10.2.0/db_1/startup.log
OK
startup.log
/u01/app/oracle/oracle/product/10.2.0/db_1/bin/dbstart: Starting up database "sales"
Thu Dec 24 23:02:00 IST 2009
logger: Can't find init file for Database instance "sales".
logger: Error: Database instance "sales" NOT started.
init.ora
# $Header: init.ora 06-aug-98.10:24:40 atsukerm Exp $
# Copyright (c) 1991, 1997, 1998 by Oracle Corporation
# NAME
# init.ora
# FUNCTION
# NOTES
# MODIFIED
# atsukerm 08/06/98 - fix for 8.1.
# hpiao 06/05/97 - fix for 803
# glavash 05/12/97 - add oracle_trace_enable comment
# hpiao 04/22/97 - remove ifile=, events=, etc.
# alingelb 09/19/94 - remove vms-specific stuff
# dpawson 07/07/93 - add more comments regarded archive start
# maporter 10/29/92 - Add vms_sga_use_gblpagfile=TRUE
# jloaiza 03/07/92 - change ALPHA to BETA
# danderso 02/26/92 - change db_block_cache_protect to dbblock_cache_p
# ghallmar 02/03/92 - db_directory -> db_domain
# maporter 01/12/92 - merge changes from branch 1.8.308.1
# maporter 12/21/91 - bug 76493: Add control_files parameter
# wbridge 12/03/91 - use of %c in archive format is discouraged
# ghallmar 12/02/91 - add global_names=true, db_directory=us.acme.com
# thayes 11/27/91 - Change default for cache_clone
# jloaiza 08/13/91 - merge changes from branch 1.7.100.1
# jloaiza 07/31/91 - add debug stuff
# rlim 04/29/91 - removal of char_is_varchar2
# Bridge 03/12/91 - log_allocation no longer exists
# Wijaya 02/05/91 - remove obsolete parameters
# Example INIT.ORA file
# This file is provided by Oracle Corporation to help you customize
# your RDBMS installation for your site. Important system parameters
# are discussed, and example settings given.
# Some parameter settings are generic to any size installation.
# For parameters that require different values in different size
# installations, three scenarios have been provided: SMALL, MEDIUM
# and LARGE. Any parameter that needs to be tuned according to
# installation size will have three settings, each one commented
# according to installation size.
# Use the following table to approximate the SGA size needed for the
# three scenarious provided in this file:
# -------Installation/Database Size------
# SMALL MEDIUM LARGE
# Block 2K 4500K 6800K 17000K
# Size 4K 5500K 8800K 21000K
# To set up a database that multiple instances will be using, place
# all instance-specific parameters in one file, and then have all
# of these files point to a master file using the IFILE command.
# This way, when you change a public
# parameter, it will automatically change on all instances. This is
# necessary, since all instances must run with the same value for many
# parameters. For example, if you choose to use private rollback segments,
# these must be specified in different files, but since all gc_*
# parameters must be the same on all instances, they should be in one file.
# INSTRUCTIONS: Edit this file and the other INIT files it calls for
# your site, either by using the values provided here or by providing
# your own. Then place an IFILE= line into each instance-specific
# INIT file that points at this file.
# NOTE: Parameter values suggested in this file are based on conservative
# estimates for computer memory availability. You should adjust values upward
# for modern machines.
# You may also consider using Database Configuration Assistant tool (DBCA)
# to create INIT file and to size your initial set of tablespaces based
# on the user input.
# replace DEFAULT with your database name
db_name=sales
db_files = 80 # SMALL
# db_files = 400 # MEDIUM
# db_files = 1500 # LARGE
db_file_multiblock_read_count = 8 # SMALL
# db_file_multiblock_read_count = 16 # MEDIUM
# db_file_multiblock_read_count = 32 # LARGE
db_block_buffers = 100 # SMALL
# db_block_buffers = 550 # MEDIUM
# db_block_buffers = 3200 # LARGE
shared_pool_size = 3500000 # SMALL
# shared_pool_size = 5000000 # MEDIUM
# shared_pool_size = 9000000 # LARGE
log_checkpoint_interval = 10000
processes = 50 # SMALL
# processes = 100 # MEDIUM
# processes = 200 # LARGE
parallel_max_servers = 5 # SMALL
# parallel_max_servers = 4 x (number of CPUs) # MEDIUM
# parallel_max_servers = 4 x (number of CPUs) # LARGE
log_buffer = 32768 # SMALL
# log_buffer = 32768 # MEDIUM
# log_buffer = 163840 # LARGE
# audit_trail = true # if you want auditing
# timed_statistics = true # if you want timed statistics
max_dump_file_size = 10240 # limit trace file size to 5 Meg each
# Uncommenting the line below will cause automatic archiving if archiving has
# been enabled using ALTER DATABASE ARCHIVELOG.
# log_archive_start = true
# log_archive_dest = disk$rdbms:[oracle.archive]
# log_archive_format = "T%TS%S.ARC"
# If using private rollback segments, place lines of the following
# form in each of your instance-specific init.ora files:
# rollback_segments = (name1, name2)
# If using public rollback segments, define how many
# rollback segments each instance will pick up, using the formula
# # of rollback segments = transactions / transactions_per_rollback_segment
# In this example each instance will grab 40/5 = 8:
# transactions = 40
# transactions_per_rollback_segment = 5
# Global Naming -- enforce that a dblink has same name as the db it connects to
global_names = TRUE
# Edit and uncomment the following line to provide the suffix that will be
# appended to the db_name parameter (separated with a dot) and stored as the
# global database name when a database is created. If your site uses
# Internet Domain names for e-mail, then the part of your e-mail address after
# the '@' is a good candidate for this parameter value.
# db_domain = us.acme.com # global database name is db_name.db_domain
# FOR DEVELOPMENT ONLY, ALWAYS TRY TO USE SYSTEM BACKING STORE
# vms_sga_use_gblpagfil = TRUE
# FOR BETA RELEASE ONLY. Enable debugging modes. Note that these can
# adversely affect performance. On some non-VMS ports the db_block_cache_*
# debugging modes have a severe effect on performance.
#_db_block_cache_protect = true # memory protect buffers
#event = "10210 trace name context forever, level 2" # data block checking
#event = "10211 trace name context forever, level 2" # index block checking
#event = "10235 trace name context forever, level 1" # memory heap checking
#event = "10049 trace name context forever, level 2" # memory protect cursors
# define parallel server (multi-instance) parameters
#ifile = ora_system:initps.ora
# define two control files by default
control_files = (ora_control1, ora_control2)
# Uncomment the following line if you wish to enable the Oracle Trace product
# to trace server activity. This enables scheduling of server collections
# from the Oracle Enterprise Manager Console.
# Also, if the oracle_trace_collection_name parameter is non-null,
# every session will write to the named collection, as well as enabling you
# to schedule future collections from the console.
# oracle_trace_enable = TRUE
# Uncomment the following line, if you want to use some of the new 8.1
# features. Please remember that using them may require some downgrade
# actions if you later decide to move back to 8.0.
#compatible = 8.1.0

starts up the instance and shuts down immediately.
Here is the log
/u01/app/oracle/oracle/product/10.2.0/db_1/bin/dbstart: Starting up database "sales"
Thu Dec 24 23:26:47 IST 2009
SQL*Plus: Release 10.2.0.1.0 - Production on Thu Dec 24 23:26:47 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
SQL> Connected to an idle instance.
SQL> ORA-00371: not enough shared pool memory, should be atleast 62198988 bytes
SQL> Disconnected
/u01/app/oracle/oracle/product/10.2.0/db_1/bin/dbstart: Database instance "sales" warm started.

ORA-25138

Hi guru,
Im doing R3SETUP -f DBMIG.R3S to oracle 10g but i hit error at this phase DBCREATEDB_IND_ORA
the error is -->
INFO 2008-02-13 15:46:53
    Creating the Database
INFO 2008-02-13 15:46:53 DBCREATEDB_IND_ORA SyPermissionSet:100
    Changing the permission of file orascr.sql to 666 ...
INFO 2008-02-13 15:46:53 DBCREATEDB_IND_ORA InternalInstallationDo:0
    Create Database.
INFO 2008-02-13 15:46:53 DBCREATEDB_IND_ORA SyCoprocessCreateAsUser:300
    Creating coprocess /oracle/PRD/102_64/bin/sqlplus /NOLOG
    @orascr.sql as user oraprd and group dba ...
INFO 2008-02-13 15:46:53 DBCREATEDB_IND_ORA SyGroupIDGet:100
    Group id for group dba is 108.
INFO 2008-02-13 15:46:53 DBCREATEDB_IND_ORA SyUserIDGet:300
    User id for user oraprd is 110.
INFO 2008-02-13 15:46:53 DBCREATEDB_IND_ORA SvrmgrDoDummy:0
    Return from DB: 25138.
INFO 2008-02-13 15:46:53 DBCREATEDB_IND_ORA SvrmgrDoDummy:0
    SQL*Plus: Release 10.2.0.2.0 - Production on Wed Feb 13 15:46:53
    2008
    Copyright (c) 1982, 2005, Oracle. All Rights Reserved.
    Connected to an idle instance.
    SQL> SET TERMOUT ON;
    SQL> SHUTDOWN ABORT;
    ORACLE instance shut down.
    SQL> STARTUP NOMOUNT PFILE=init.ora;
    ORA-25138: ENQUEUE_RESOURCES initialization parameter has been
    made obsolete
    ORA-32006: LOG_ARCHIVE_START initialization parameter has been
    deprecated
    ORA-25138: TRANSACTION_AUDITING initialization parameter has been
    made obsolete
    ORA-25138: HASH_JOIN_ENABLED initialization parameter has been
    made obsolete
    ORA-00381: cannot use both new and old parameters for buffer
    cache size specification
    SQL> CREATE DATABASE PRD
      2 CONTROLFILE REUSE
      3 MAXDATAFILES 254
      4 MAXLOGFILES   255
      5 MAXLOGHISTORY 1000
      6 MAXLOGMEMBERS 3
      7 MAXINSTANCES 50
      8 NOARCHIVELOG
      9 CHARACTER SET "WE8DEC"
     10 DATAFILE
     11 '/oracle/PRD/sapdata1/system_1/system.data1' SIZE 200M REUSE
     12 AUTOEXTEND ON NEXT 20M MAXSIZE 10000M EXTENT MANAGEMENT
    LOCAL
     13 DEFAULT TEMPORARY TABLESPACE PSAPTEMP TEMPFILE
     14 '/oracle/PRD/sapdata1/temp_1/temp.data1' SIZE 300M REUSE
     15 AUTOEXTEND ON NEXT 20M MAXSIZE 10000M
     16 UNDO TABLESPACE PSAPUNDO DATAFILE
INFO 2008-02-13 15:46:53 DBCREATEDB_IND_ORA SvrmgrDoDummy:0
     17 '/oracle/PRD/sapdata1/roll_1/roll.data1' SIZE 650M REUSE
     18 AUTOEXTEND ON NEXT 20M MAXSIZE 10000M
     19 SYSAUX DATAFILE
     20 '/oracle/PRD/sapdata1/sysaux_1/sysaux.data1' SIZE 100M REUSE
     21 AUTOEXTEND ON NEXT 20M MAXSIZE 10000M
     22 LOGFILE
     23 GROUP 11 (
     24 '/oracle/PRD/origlogA/log_g11m1.dbf',
     25 '/oracle/PRD/mirrlogA/log_g11m2.dbf'
     26 ) SIZE 20M REUSE
     27 ,GROUP 13 (
     28 '/oracle/PRD/origlogA/log_g13m1.dbf',
     29 '/oracle/PRD/mirrlogA/log_g13m2.dbf'
     30 ) SIZE 20M REUSE
     31 ,GROUP 12 (
     32 '/oracle/PRD/origlogB/log_g12m1.dbf',
     33 '/oracle/PRD/mirrlogB/log_g12m2.dbf'
     34 ) SIZE 20M REUSE
     35 ,GROUP 14 (
     36 '/oracle/PRD/origlogB/log_g14m1.dbf',
     37 '/oracle/PRD/mirrlogB/log_g14m2.dbf'
     38 ) SIZE 20M REUSE
     39 ;
    CREATE DATABASE PRD
    ERROR at line 1:
    ORA-01034: ORACLE not available
    SQL> EXIT
    Disconnected
ERROR 2008-02-13 15:46:53 DBCREATEDB_IND_ORA InternalInstallationDo:0
    Create Database failed errorcode = 25138.
ERROR 2008-02-13 15:46:53 DBCREATEDB_IND_ORA InstallationDo:0
    Phase failed.
ERROR 2008-02-13 15:46:53 InstController Action:0
    Step DBCREATEDB_IND_ORA could not be performed.
ERROR 2008-02-13 15:46:54 Main
    Installation failed.
ERROR 2008-02-13 15:46:54 Main
    Installation aborted.
Hope can assistme..im running out time to do upgrade ECC6
zakie

Here my init .ora
please guy..
replace DEFAULT with your database name
db_name=DEFAULT
db_files = 80                                                         # SMALL
db_files = 400                                                      # MEDIUM
db_files = 1500                                                     # LARGE
db_file_multiblock_read_count = 16                                  # MEDIUM
db_file_multiblock_read_count = 32                                  # LARGE
#db_block_buffers = 550                                              # MEDIUM
db_block_buffers = 3200                                             # LARGE
#shared_pool_size = 3500000
shared_pool_size = 123232153                                           # SMALL
shared_pool_size = 5000000                                          # MEDIUM
shared_pool_size = 9000000                                          # LARGE
log_checkpoint_interval = 10000
processes = 50                                                        # SMALL
processes = 100                                                     # MEDIUM
processes = 200                                                     # LARGE
parallel_max_servers = 5                                              # SMALL
parallel_max_servers = 4 x (number of CPUs)                         # MEDIUM
parallel_max_servers = 4 x (number of CPUs)                         # LARGE
log_buffer = 32768                                                    # SMALL
log_buffer = 32768                                                  # MEDIUM
log_buffer = 163840                                                 # LARGE
audit_trail = true            # if you want auditing
timed_statistics = true       # if you want timed statistics
max_dump_file_size = 10240      # limit trace file size to 5 Meg each
Uncommenting the line below will cause automatic archiving if archiving has
been enabled using ALTER DATABASE ARCHIVELOG.
log_archive_start = true
log_archive_dest = disk$rdbms:[oracle.archive]
log_archive_format = "T%TS%S.ARC"
If using private rollback segments, place lines of the following
form in each of your instance-specific init.ora files:
rollback_segments = (name1, name2)
If using public rollback segments, define how many
rollback segments each instance will pick up, using the formula
# of rollback segments = transactions / transactions_per_rollback_segment
In this example each instance will grab 40/5 = 8:
transactions = 40
transactions_per_rollback_segment = 5
Global Naming -- enforce that a dblink has same name as the db it connects to
global_names = TRUE
Edit and uncomment the following line to provide the suffix that will be
appended to the db_name parameter (separated with a dot) and stored as the
global database name when a database is created. If your site uses
Internet Domain names for e-mail, then the part of your e-mail address after
the '@' is a good candidate for this parameter value.
db_domain = us.acme.com       # global database name is db_name.db_domain
FOR DEVELOPMENT ONLY, ALWAYS TRY TO USE SYSTEM BACKING STORE
vms_sga_use_gblpagfil = TRUE
FOR BETA RELEASE ONLY. Enable debugging modes. Note that these can
adversely affect performance. On some non-VMS ports the db_block_cache_*
debugging modes have a severe effect on performance.
#_db_block_cache_protect = true                       # memory protect buffers
#event = "10210 trace name context forever, level 2" # data block checking
#event = "10211 trace name context forever, level 2" # index block checking
#event = "10235 trace name context forever, level 1" # memory heap checking
#event = "10049 trace name context forever, level 2" # memory protect cursors
define parallel server (multi-instance) parameters
#ifile = ora_system:initps.ora
define two control files by default
control_files = (ora_control1, ora_control2)
Uncomment the following line if you wish to enable the Oracle Trace product
to trace server activity. This enables scheduling of server collections
from the Oracle Enterprise Manager Console.
Also, if the oracle_trace_collection_name parameter is non-null,
every session will write to the named collection, as well as enabling you
to schedule future collections from the console.
oracle_trace_enable = TRUE
Uncomment the following line, if you want to use some of the new 8.1
features. Please remember that using them may require some downgrade
actions if you later decide to move back to 8.0.
#compatible = 8.1.0

Configure Mobile BO out of my network

Hi experts,
I have installed BO Mobile 3.1
All work fine if i´m in my private network, but, if i go out my network don´t work, why?
I do a redirection of ports with a public IP and ports 6400, 11011, 11711, 8080 and in my mobile client:
Mobile server:
Are there any wrong?
Thanks in advance,
Regards,

It works now...
I replaced the hostname with the ip-addresses in the VAS and VMS server-config, then it worked.
VAS:
[comm $ external $ default]
EXTERNAL_HOSTNAME= <external IP-Address of the mobile-server>
EXTERNAL_PORT= <external VAS-port of the mobile-server>
CLIENT_TYPE=any
CLIENT_HOSTNAME=0.0.0.0
VMS:
[comm $ external $ default]
EXTERNAL_HOSTNAME= <external IP-Address of the mobile-server>
EXTERNAL_PORT=<external VMS-port of the mobile-server>
CLIENT_TYPE=any
CLIENT_HOSTNAME=0.0.0.0
From the mobile device (windows mobile), only the ip-address was reachable, but not the hostname (tested with a ping-programm from the mobile device).

Bo Mobile Authentication Problem

i use MDS 4.1.4 and bb simulator 9530
bo is the same place with mds and bb simulator.
mds and bo in the same server:192.168.1.66 local ip.and machine name is botest(mobile server is in the same place too)
VAS-cluster config:
i added:
[comm]
[comm $ mds]
HOST_PORT =192.168.1.66:8888
VAS-server.config:
i added:
[comm $ external]
ENABLED=mds
[comm $ external $ mds]
EXTERNAL_HOSTNAME=BOTEST
CLIENT_TYPE=mds
VMS-server.config:
i added:
[comm $ external]
ENABLED=mds
[comm $ external $ mds]
EXTERNAL_HOSTNAME=BOTEST
CLIENT_TYPE=mds
in this situation i connect to the cms with a bb simulator..but in a real bb says to me " authentication login...."
what is the problem?
thanks in advance.

Hi,
Also, in a real BB deployment, the request would go through a BES server deployment.
Make sure the settings are apt on teh BES server side ( ip:port)
Also, the VAS and VMS ports are open between BO and BES server.
Regards,
Atul

Need a script to import the data from flat file

Hi Friends,
Any one have any scripts to import the data from flat files into oracle database(Linux OS). I have to automate the script for every 30min to check any flat files in Incoming directory process them with out user interaction.
Thanks.
Srini

Here is my init.ora file
# $Header: init.ora 06-aug-98.10:24:40 atsukerm Exp $
# Copyright (c) 1991, 1997, 1998 by Oracle Corporation
# NAME
# init.ora
# FUNCTION
# NOTES
# MODIFIED
# atsukerm 08/06/98 - fix for 8.1.
# hpiao 06/05/97 - fix for 803
# glavash 05/12/97 - add oracle_trace_enable comment
# hpiao 04/22/97 - remove ifile=, events=, etc.
# alingelb 09/19/94 - remove vms-specific stuff
# dpawson 07/07/93 - add more comments regarded archive start
# maporter 10/29/92 - Add vms_sga_use_gblpagfile=TRUE
# jloaiza 03/07/92 - change ALPHA to BETA
# danderso 02/26/92 - change db_block_cache_protect to dbblock_cache_p
# ghallmar 02/03/92 - db_directory -> db_domain
# maporter 01/12/92 - merge changes from branch 1.8.308.1
# maporter 12/21/91 - bug 76493: Add control_files parameter
# wbridge 12/03/91 - use of %c in archive format is discouraged
# ghallmar 12/02/91 - add global_names=true, db_directory=us.acme.com
# thayes 11/27/91 - Change default for cache_clone
# jloaiza 08/13/91 - merge changes from branch 1.7.100.1
# jloaiza 07/31/91 - add debug stuff
# rlim 04/29/91 - removal of char_is_varchar2
# Bridge 03/12/91 - log_allocation no longer exists
# Wijaya 02/05/91 - remove obsolete parameters
# Example INIT.ORA file
# This file is provided by Oracle Corporation to help you customize
# your RDBMS installation for your site. Important system parameters
# are discussed, and example settings given.
# Some parameter settings are generic to any size installation.
# For parameters that require different values in different size
# installations, three scenarios have been provided: SMALL, MEDIUM
# and LARGE. Any parameter that needs to be tuned according to
# installation size will have three settings, each one commented
# according to installation size.
# Use the following table to approximate the SGA size needed for the
# three scenarious provided in this file:
# -------Installation/Database Size------
# SMALL MEDIUM LARGE
# Block 2K 4500K 6800K 17000K
# Size 4K 5500K 8800K 21000K
# To set up a database that multiple instances will be using, place
# all instance-specific parameters in one file, and then have all
# of these files point to a master file using the IFILE command.
# This way, when you change a public
# parameter, it will automatically change on all instances. This is
# necessary, since all instances must run with the same value for many
# parameters. For example, if you choose to use private rollback segments,
# these must be specified in different files, but since all gc_*
# parameters must be the same on all instances, they should be in one file.
# INSTRUCTIONS: Edit this file and the other INIT files it calls for
# your site, either by using the values provided here or by providing
# your own. Then place an IFILE= line into each instance-specific
# INIT file that points at this file.
# NOTE: Parameter values suggested in this file are based on conservative
# estimates for computer memory availability. You should adjust values upward
# for modern machines.
# You may also consider using Database Configuration Assistant tool (DBCA)
# to create INIT file and to size your initial set of tablespaces based
# on the user input.
# replace DEFAULT with your database name
db_name=DEFAULT
db_files = 80 # SMALL
# db_files = 400 # MEDIUM
# db_files = 1500 # LARGE
db_file_multiblock_read_count = 8 # SMALL
# db_file_multiblock_read_count = 16 # MEDIUM
# db_file_multiblock_read_count = 32 # LARGE
db_block_buffers = 100 # SMALL
# db_block_buffers = 550 # MEDIUM
# db_block_buffers = 3200 # LARGE
shared_pool_size = 3500000 # SMALL
# shared_pool_size = 5000000 # MEDIUM
# shared_pool_size = 9000000 # LARGE
log_checkpoint_interval = 10000
processes = 50 # SMALL
# processes = 100 # MEDIUM
# processes = 200 # LARGE
parallel_max_servers = 5 # SMALL
# parallel_max_servers = 4 x (number of CPUs) # MEDIUM
# parallel_max_servers = 4 x (number of CPUs) # LARGE
log_buffer = 32768 # SMALL
# log_buffer = 32768 # MEDIUM
# log_buffer = 163840 # LARGE
# audit_trail = true # if you want auditing
# timed_statistics = true # if you want timed statistics
max_dump_file_size = 10240 # limit trace file size to 5 Meg each
# Uncommenting the line below will cause automatic archiving if archiving has
# been enabled using ALTER DATABASE ARCHIVELOG.
# log_archive_start = true
# log_archive_dest = disk$rdbms:[oracle.archive]
# log_archive_format = "T%TS%S.ARC"
# If using private rollback segments, place lines of the following
# form in each of your instance-specific init.ora files:
# rollback_segments = (name1, name2)
# If using public rollback segments, define how many
# rollback segments each instance will pick up, using the formula
# # of rollback segments = transactions / transactions_per_rollback_segment
# In this example each instance will grab 40/5 = 8:
# transactions = 40
# transactions_per_rollback_segment = 5
# Global Naming -- enforce that a dblink has same name as the db it connects to
global_names = TRUE
# Edit and uncomment the following line to provide the suffix that will be
# appended to the db_name parameter (separated with a dot) and stored as the
# global database name when a database is created. If your site uses
# Internet Domain names for e-mail, then the part of your e-mail address after
# the '@' is a good candidate for this parameter value.
# db_domain = us.acme.com # global database name is db_name.db_domain
# FOR DEVELOPMENT ONLY, ALWAYS TRY TO USE SYSTEM BACKING STORE
# vms_sga_use_gblpagfil = TRUE
# FOR BETA RELEASE ONLY. Enable debugging modes. Note that these can
# adversely affect performance. On some non-VMS ports the db_block_cache_*
# debugging modes have a severe effect on performance.
#_db_block_cache_protect = true # memory protect buffers
#event = "10210 trace name context forever, level 2" # data block checking
#event = "10211 trace name context forever, level 2" # index block checking
#event = "10235 trace name context forever, level 1" # memory heap checking
#event = "10049 trace name context forever, level 2" # memory protect cursors
# define parallel server (multi-instance) parameters
#ifile = ora_system:initps.ora
# define two control files by default
control_files = (ora_control1, ora_control2)
# Uncomment the following line if you wish to enable the Oracle Trace product
# to trace server activity. This enables scheduling of server collections
# from the Oracle Enterprise Manager Console.
# Also, if the oracle_trace_collection_name parameter is non-null,
# every session will write to the named collection, as well as enabling you
# to schedule future collections from the console.
# oracle_trace_enable = TRUE
# Uncomment the following line, if you want to use some of the new 8.1
# features. Please remember that using them may require some downgrade
# actions if you later decide to move back to 8.0.
#compatible = 8.1.0
Thanks.
Srini

Ora-12547 and ora-12560 Great Problem

Hello. Sorry for my english.
I've a great problem.
My server hp with 4 processor and 8 gb memory and oracle 9.2.0.6 and linux Red Hat Advanced Server have one great problem. If the connected user are 70 or more , I can't connect from the client with sqlplus name/password@service_name, but I can connect from the server with sqlplus name/password. sqlplus give me ora-12547 and if I launch sqlplus and after write user and password it give me ora-12560
If the session are 69 or less I can connect from the client and I can connect from the server.
The main applicatio work becaus it call oracle directly from server, but when the users are more then 70 I can't use odbc or Enterprise Manager Console from the client.
Any ideas ? Thank you.
Luca

MY INIT.ORA
# $Header: init.ora 06-aug-98.10:24:40 atsukerm Exp $
# Copyright (c) 1991, 1997, 1998 by Oracle Corporation
# NAME
# init.ora
# FUNCTION
# NOTES
# MODIFIED
# atsukerm 08/06/98 - fix for 8.1.
# hpiao 06/05/97 - fix for 803
# glavash 05/12/97 - add oracle_trace_enable comment
# hpiao 04/22/97 - remove ifile=, events=, etc.
# alingelb 09/19/94 - remove vms-specific stuff
# dpawson 07/07/93 - add more comments regarded archive start
# maporter 10/29/92 - Add vms_sga_use_gblpagfile=TRUE
# jloaiza 03/07/92 - change ALPHA to BETA
# danderso 02/26/92 - change db_block_cache_protect to dbblock_cache_p
# ghallmar 02/03/92 - db_directory -> db_domain
# maporter 01/12/92 - merge changes from branch 1.8.308.1
# maporter 12/21/91 - bug 76493: Add control_files parameter
# wbridge 12/03/91 - use of %c in archive format is discouraged
# ghallmar 12/02/91 - add global_names=true, db_directory=us.acme.com
# thayes 11/27/91 - Change default for cache_clone
# jloaiza 08/13/91 - merge changes from branch 1.7.100.1
# jloaiza 07/31/91 - add debug stuff
# rlim 04/29/91 - removal of char_is_varchar2
# Bridge 03/12/91 - log_allocation no longer exists
# Wijaya 02/05/91 - remove obsolete parameters
# Example INIT.ORA file
# This file is provided by Oracle Corporation to help you customize
# your RDBMS installation for your site. Important system parameters
# are discussed, and example settings given.
# Some parameter settings are generic to any size installation.
# For parameters that require different values in different size
# installations, three scenarios have been provided: SMALL, MEDIUM
# and LARGE. Any parameter that needs to be tuned according to
# installation size will have three settings, each one commented
# according to installation size.
# Use the following table to approximate the SGA size needed for the
# three scenarious provided in this file:
# -------Installation/Database Size------
# SMALL MEDIUM LARGE
# Block 2K 4500K 6800K 17000K
# Size 4K 5500K 8800K 21000K
# To set up a database that multiple instances will be using, place
# all instance-specific parameters in one file, and then have all
# of these files point to a master file using the IFILE command.
# This way, when you change a public
# parameter, it will automatically change on all instances. This is
# necessary, since all instances must run with the same value for many
# parameters. For example, if you choose to use private rollback segments,
# these must be specified in different files, but since all gc_*
# parameters must be the same on all instances, they should be in one file.
# INSTRUCTIONS: Edit this file and the other INIT files it calls for
# your site, either by using the values provided here or by providing
# your own. Then place an IFILE= line into each instance-specific
# INIT file that points at this file.
# NOTE: Parameter values suggested in this file are based on conservative
# estimates for computer memory availability. You should adjust values upward
# for modern machines.
# You may also consider using Database Configuration Assistant tool (DBCA)
# to create INIT file and to size your initial set of tablespaces based
# on the user input.
# replace DEFAULT with your database name
db_name=DEFAULT
db_files = 80 # SMALL
# db_files = 400 # MEDIUM
# db_files = 1500 # LARGE
db_file_multiblock_read_count = 8 # SMALL
# db_file_multiblock_read_count = 16 # MEDIUM
# db_file_multiblock_read_count = 32 # LARGE
db_block_buffers = 100 # SMALL
# db_block_buffers = 550 # MEDIUM
# db_block_buffers = 3200 # LARGE
shared_pool_size = 3500000 # SMALL
# shared_pool_size = 5000000 # MEDIUM
# shared_pool_size = 9000000 # LARGE
log_checkpoint_interval = 10000
processes = 50 # SMALL
# processes = 100 # MEDIUM
# processes = 200 # LARGE
parallel_max_servers = 5 # SMALL
# parallel_max_servers = 4 x (number of CPUs) # MEDIUM
# parallel_max_servers = 4 x (number of CPUs) # LARGE
log_buffer = 32768 # SMALL
# log_buffer = 32768 # MEDIUM
# log_buffer = 163840 # LARGE
# audit_trail = true # if you want auditing
# timed_statistics = true # if you want timed statistics
max_dump_file_size = 10240 # limit trace file size to 5 Meg each
# Uncommenting the line below will cause automatic archiving if archiving has
# been enabled using ALTER DATABASE ARCHIVELOG.
# log_archive_start = true
# log_archive_dest = disk$rdbms:[oracle.archive]
# log_archive_format = "T%TS%S.ARC"
# If using private rollback segments, place lines of the following
# form in each of your instance-specific init.ora files:
# rollback_segments = (name1, name2)
# If using public rollback segments, define how many
# rollback segments each instance will pick up, using the formula
# # of rollback segments = transactions / transactions_per_rollback_segment
# In this example each instance will grab 40/5 = 8:
# transactions = 40
# transactions_per_rollback_segment = 5
# Global Naming -- enforce that a dblink has same name as the db it connects to
global_names = TRUE
# Edit and uncomment the following line to provide the suffix that will be
# appended to the db_name parameter (separated with a dot) and stored as the
# global database name when a database is created. If your site uses
# Internet Domain names for e-mail, then the part of your e-mail address after
# the '@' is a good candidate for this parameter value.
# db_domain = us.acme.com # global database name is db_name.db_domain
# FOR DEVELOPMENT ONLY, ALWAYS TRY TO USE SYSTEM BACKING STORE
# vms_sga_use_gblpagfil = TRUE
# FOR BETA RELEASE ONLY. Enable debugging modes. Note that these can
# adversely affect performance. On some non-VMS ports the db_block_cache_*
# debugging modes have a severe effect on performance.
#_db_block_cache_protect = true # memory protect buffers
#event = "10210 trace name context forever, level 2" # data block checking
#event = "10211 trace name context forever, level 2" # index block checking
#event = "10235 trace name context forever, level 1" # memory heap checking
#event = "10049 trace name context forever, level 2" # memory protect cursors
# define parallel server (multi-instance) parameters
#ifile = ora_system:initps.ora
# define two control files by default
control_files = (ora_control1, ora_control2)
# Uncomment the following line if you wish to enable the Oracle Trace product
# to trace server activity. This enables scheduling of server collections
# from the Oracle Enterprise Manager Console.
# Also, if the oracle_trace_collection_name parameter is non-null,
# every session will write to the named collection, as well as enabling you
# to schedule future collections from the console.
# oracle_trace_enable = TRUE
# Uncomment the following line, if you want to use some of the new 8.1
# features. Please remember that using them may require some downgrade
# actions if you later decide to move back to 8.0.
#compatible = 8.1.0

DB won't monut or start

The following is what I do and what happens. The Database won't mount or start. Please advise:
[oracle@DiNA oracle]$ sqlplus /nolog
SQL*Plus: Release 9.2.0.1.0 - Production on Mon Sep 8 08:08:57 2003
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
SQL> connect / as sysdba
Connected to an idle instance.
SQL> startup
ORACLE instance started.
Total System Global Area 42741800 bytes
Fixed Size 450600 bytes
Variable Size 41943040 bytes
Database Buffers 204800 bytes
Redo Buffers 143360 bytes
ORA-00205: error in identifying controlfile, check alert log for more info

Ok, here is what my inittest.ora file looks like. It shows where control files were initiated. What do I do from here?
# replace DEFAULT with your database name
db_name=test
db_files = 80 # SMALL
# db_files = 400 # MEDIUM
# db_files = 1500 # LARGE
db_file_multiblock_read_count = 8 # SMALL
# db_file_multiblock_read_count = 16 # MEDIUM
# db_file_multiblock_read_count = 32 # LARGE
db_block_buffers = 100 # SMALL
# db_block_buffers = 550 # MEDIUM
# db_block_buffers = 3200 # LARGE
shared_pool_size = 3500000 # SMALL
# shared_pool_size = 5000000 # MEDIUM
# shared_pool_size = 9000000 # LARGE
log_checkpoint_interval = 10000
processes = 50 # SMALL
# processes = 100 # MEDIUM
# processes = 200 # LARGE
parallel_max_servers = 5 # SMALL
# parallel_max_servers = 4 x (number of CPUs) # MEDIUM
# parallel_max_servers = 4 x (number of CPUs) # LARGE
log_buffer = 32768 # SMALL
# log_buffer = 32768 # MEDIUM
# log_buffer = 163840 # LARGE
# audit_trail = true # if you want auditing
# timed_statistics = true # if you want timed statistics
max_dump_file_size = 10240 # limit trace file size to 5 Meg each
# Uncommenting the line below will cause automatic archiving if archiving has
# been enabled using ALTER DATABASE ARCHIVELOG.
# log_archive_start = true
# log_archive_dest = disk$rdbms:[oracle.archive]
# log_archive_format = "T%TS%S.ARC"
# If using private rollback segments, place lines of the following
# form in each of your instance-specific init.ora files:
# rollback_segments = (name1, name2)
# If using public rollback segments, define how many
# rollback segments each instance will pick up, using the formula
# # of rollback segments = transactions / transactions_per_rollback_segment
# In this example each instance will grab 40/5 = 8:
# transactions = 40
# transactions_per_rollback_segment = 5
# Global Naming -- enforce that a dblink has same name as the db it connects to
global_names = TRUE
# Edit and uncomment the following line to provide the suffix that will be
# appended to the db_name parameter (separated with a dot) and stored as the
# global database name when a database is created. If your site uses
# Internet Domain names for e-mail, then the part of your e-mail address after
# the '@' is a good candidate for this parameter value.
# db_domain = us.acme.com # global database name is db_name.db_domain
# FOR DEVELOPMENT ONLY, ALWAYS TRY TO USE SYSTEM BACKING STORE
# vms_sga_use_gblpagfil = TRUE
# FOR BETA RELEASE ONLY. Enable debugging modes. Note that these can
# adversely affect performance. On some non-VMS ports the db_block_cache_*
# debugging modes have a severe effect on performance.
#_db_block_cache_protect = true # memory protect buffers
#event = "10210 trace name context forever, level 2" # data block checking
#event = "10211 trace name context forever, level 2" # index block checking
#event = "10235 trace name context forever, level 1" # memory heap checking
#event = "10049 trace name context forever, level 2" # memory protect cursors
# define parallel server (multi-instance) parameters
#ifile = ora_system:initps.ora
# define two control files by default
control_files = (ora_control1, ora_control2)
# Uncomment the following line if you wish to enable the Oracle Trace product
# to trace server activity. This enables scheduling of server collections
# from the Oracle Enterprise Manager Console.
# Also, if the oracle_trace_collection_name parameter is non-null,
# every session will write to the named collection, as well as enabling you
# to schedule future collections from the console.
# oracle_trace_enable = TRUE
# Uncomment the following line, if you want to use some of the new 8.1
# features. Please remember that using them may require some downgrade
# actions if you later decide to move back to 8.0.
#compatible = 8.1.0
Please advise.

How to create pfile..

Hi guys,
The first step in creating a database manually is to create a pfile so that later on we can create a spfile from this pfile through command:
create spfile from pfile;
my question is how to create this pfile???
please help.
Imran Baig

If you do not have a spfile created you can take the model found in : <ORACLE_HOME>/dbs/init.ora
[oracle@ozawa dump]$ cd $ORACLE_HOME/dbs
[oracle@ozawa dbs]$
[oracle@ozawa dbs]$ ll
total 76
-rw-r--r-- 1 oracle oracle 12920 Mar 9 2002 initdw.ora
-rw-r--r-- 1 oracle oracle 8385 Mar 9 2002 init.ora
-rw-rw---- 1 oracle oracle 24 Jan 6 18:24 lkLCONVCLA
-rw-rw---- 1 oracle oracle 24 Feb 16 14:15 lkLDEVCARD
-rw-rw---- 1 oracle oracle 24 Dec 28 15:41 lkLDEVCNS0
-rw-rw---- 1 oracle oracle 24 Feb 8 09:24 lkLQACNS1
-rwSr----- 1 oracle oracle 1536 Jan 7 08:55 orapwLCONVCLA
-rwSr----- 1 oracle oracle 1536 Jan 6 16:17 orapwLDEVCARD
-rwSr----- 1 oracle oracle 1536 Jan 7 16:53 orapwLDEVCNS0
-rwSr----- 1 oracle oracle 1536 Feb 11 08:34 orapwLQACNS1
-rw-rw---- 1 oracle oracle 2560 Jan 6 18:24 spfileLCONVCLA.ora
-rw-rw---- 1 oracle oracle 2560 Jan 6 14:05 spfileLDEVCARD.ora
-rw-rw---- 1 oracle oracle 2560 Jan 4 11:12 spfileLDEVCNS0.ora
-rw-rw---- 1 oracle oracle 2560 Feb 6 17:09 spfileLQACNS1.ora
[oracle@ozawa dbs]$
[oracle@ozawa dbs]$
[oracle@ozawa dbs]$ more init.ora
# $Header: init.ora 06-aug-98.10:24:40 atsukerm Exp $
# Copyright (c) 1991, 1997, 1998 by Oracle Corporation
# NAME
# init.ora
# FUNCTION
# NOTES
# MODIFIED
# atsukerm 08/06/98 - fix for 8.1.
# hpiao 06/05/97 - fix for 803
# glavash 05/12/97 - add oracle_trace_enable comment
# hpiao 04/22/97 - remove ifile=, events=, etc.
# alingelb 09/19/94 - remove vms-specific stuff
# dpawson 07/07/93 - add more comments regarded archive start
# maporter 10/29/92 - Add vms_sga_use_gblpagfile=TRUE
# jloaiza 03/07/92 - change ALPHA to BETA
# danderso 02/26/92 - change db_block_cache_protect to dbblock_cache_p
# ghallmar 02/03/92 - db_directory -> db_domain
# maporter 01/12/92 - merge changes from branch 1.8.308.1
# maporter 12/21/91 - bug 76493: Add control_files parameter
# wbridge 12/03/91 - use of %c in archive format is discouraged
# ghallmar 12/02/91 - add global_names=true, db_directory=us.acme.com
# thayes 11/27/91 - Change default for cache_clone
# jloaiza 08/13/91 - merge changes from branch 1.7.100.1
# jloaiza 07/31/91 - add debug stuff
# rlim 04/29/91 - removal of char_is_varchar2
# Bridge 03/12/91 - log_allocation no longer exists
# Wijaya 02/05/91 - remove obsolete parameters
# Example INIT.ORA file
# This file is provided by Oracle Corporation to help you customize
# your RDBMS installation for your site. Important system parameters
# are discussed, and example settings given.
# Some parameter settings are generic to any size installation.
# For parameters that require different values in different size
# installations, three scenarios have been provided: SMALL, MEDIUM
# and LARGE. Any parameter that needs to be tuned according to
# installation size will have three settings, each one commented
# according to installation size.
# Use the following table to approximate the SGA size needed for the
# three scenarious provided in this file:
# -------Installation/Database Size------
# SMALL MEDIUM LARGE
# Block 2K 4500K 6800K 17000K
# Size 4K 5500K 8800K 21000K
# To set up a database that multiple instances will be using, place
# all instance-specific parameters in one file, and then have all
# of these files point to a master file using the IFILE command.
# This way, when you change a public
# parameter, it will automatically change on all instances. This is
# necessary, since all instances must run with the same value for many
# parameters. For example, if you choose to use private rollback segments,
# these must be specified in different files, but since all gc_*
# parameters must be the same on all instances, they should be in one file.
# INSTRUCTIONS: Edit this file and the other INIT files it calls for
# your site, either by using the values provided here or by providing
# your own. Then place an IFILE= line into each instance-specific
# INIT file that points at this file.
# NOTE: Parameter values suggested in this file are based on conservative
# estimates for computer memory availability. You should adjust values upward
# for modern machines.
# You may also consider using Database Configuration Assistant tool (DBCA)
# to create INIT file and to size your initial set of tablespaces based
# on the user input.
# replace DEFAULT with your database name
db_name=DEFAULT
db_files = 80 # SMALL
# db_files = 400 # MEDIUM
# db_files = 1500 # LARGE
db_file_multiblock_read_count = 8 # SMALL
# db_file_multiblock_read_count = 16 # MEDIUM
# db_file_multiblock_read_count = 32 # LARGE
db_block_buffers = 100 # SMALL
# db_block_buffers = 550 # MEDIUM
# db_block_buffers = 3200 # LARGE
shared_pool_size = 3500000 # SMALL
# shared_pool_size = 5000000 # MEDIUM
# shared_pool_size = 9000000 # LARGE
log_checkpoint_interval = 10000
processes = 50 # SMALL
# processes = 100 # MEDIUM
# processes = 200 # LARGE
parallel_max_servers = 5 # SMALL
# parallel_max_servers = 4 x (number of CPUs) # MEDIUM
# parallel_max_servers = 4 x (number of CPUs) # LARGE
log_buffer = 32768 # SMALL
# log_buffer = 32768 # MEDIUM
# log_buffer = 163840 # LARGE
# audit_trail = true # if you want auditing
# timed_statistics = true # if you want timed statistics
max_dump_file_size = 10240 # limit trace file size to 5 Meg each
# Uncommenting the line below will cause automatic archiving if archiving has
# been enabled using ALTER DATABASE ARCHIVELOG.
# log_archive_start = true
# log_archive_dest = disk$rdbms:[oracle.archive]
# log_archive_format = "T%TS%S.ARC"
# If using private rollback segments, place lines of the following
# form in each of your instance-specific init.ora files:
# rollback_segments = (name1, name2)
# If using public rollback segments, define how many
# rollback segments each instance will pick up, using the formula
# # of rollback segments = transactions / transactions_per_rollback_segment
# In this example each instance will grab 40/5 = 8:
# transactions = 40
# transactions_per_rollback_segment = 5
# Global Naming -- enforce that a dblink has same name as the db it connects to
global_names = TRUE
# Edit and uncomment the following line to provide the suffix that will be
# appended to the db_name parameter (separated with a dot) and stored as the
# global database name when a database is created. If your site uses
# Internet Domain names for e-mail, then the part of your e-mail address after
# the '@' is a good candidate for this parameter value.
# db_domain = us.acme.com # global database name is db_name.db_domain
# FOR DEVELOPMENT ONLY, ALWAYS TRY TO USE SYSTEM BACKING STORE
# vms_sga_use_gblpagfil = TRUE
# FOR BETA RELEASE ONLY. Enable debugging modes. Note that these can
# adversely affect performance. On some non-VMS ports the db_block_cache_*
# debugging modes have a severe effect on performance.
#_db_block_cache_protect = true # memory protect buffers
#event = "10210 trace name context forever, level 2" # data block checking
#event = "10211 trace name context forever, level 2" # index block checking
#event = "10235 trace name context forever, level 1" # memory heap checking
#event = "10049 trace name context forever, level 2" # memory protect cursors
# define parallel server (multi-instance) parameters
#ifile = ora_system:initps.ora
# define two control files by default
control_files = (ora_control1, ora_control2)
# Uncomment the following line if you wish to enable the Oracle Trace product
# to trace server activity. This enables scheduling of server collections
# from the Oracle Enterprise Manager Console.
# Also, if the oracle_trace_collection_name parameter is non-null,
# every session will write to the named collection, as well as enabling you
# to schedule future collections from the console.
# oracle_trace_enable = TRUE
# Uncomment the following line, if you want to use some of the new 8.1
# features. Please remember that using them may require some downgrade
# actions if you later decide to move back to 8.0.
#compatible = 8.1.0
[oracle@ozawa dbs]$
Joel Pérez
http://otn.oracle.com/experts

Enable Ethernet port on VMS

I wish Verizon would Enable the Enable Ethernet port on the VMS. I Have coax and ethernet in 2 rooms and ethernet in all rooms the 2 Clients are connect ethernet olny and i would like toi switch to a top of the line router but i need take the fios router out of the picture. the olny way it would be benafical to me if i could have my setup like this
VMS via ethernet for network and coax for tv
ont --> Non-Fios Router ---> Clients via eathernet
other devices (Computers via Ethernet and WiFi)
current setup
VMS via coax
ont ---> Fios router ---> Clients via ethernet
other devices (Computers via Ethernet and WiFi)
If you like this idea click thumbs up I am trying to get verizon to implment this.
I would add the settop boxes to the DMZ on my non-fios router so there is no blocked ports between the ont and the settop boxa

leave the tv single the way it is over the coax but allow the data to be sent over ethernet instead of moca(coax). so the the QAM would still be on the coax but the img guide data, on damand data and other data for the box to go over ethernet. the IPC1100 boxes would be ethernet olny as i have the set up now
VMS would have coax and ethernet hoked up to it and client boxes have ethernet olny
then there world be no need for the verizon router
over all setup would look like this
instead of the current setup like this
i have 2-3 cat6 cables in each room going through the walls the go back to the Master bedroom closet

Utilizing all ports on a 4 port NIC for VMs

I have in my environment two Dell Host, Dell N3024 iSCSI switch and an EMC-3200 storage. A Broadcom 1Gb 4 port NIC that connect the Dell host to the EMC storage via the N3024. An Intel 1Gb 4 port NIC that connects the Dell hosts to the LAN (I port in use). I have 9 VMs using the single port on the Intel NIC. I would like to increase the bandwidth to the VMs without replacing the Intel NIC. How do I configure the NIC to use all 4 ports?

Hi，
Did you mean that the issue had been solved by install the compatible Intel drivers? If yes, good to hear that and thanks for sharing.
Best regards,
Susie

I recently upgraded to Fios Quantum and have a new ActionTech router. As a result my PC is no longer communicating with my APPLE TV.It must have a firewall or ports beegin blocked preventing the homesharing and communication even though the APPLE TV is on

I recently upgraded to Verizon Fios Quantum high speed internet and was given an ActionTec router. I sucessfully installed all and connected wth my Apple TV. Although it worked initially it no longer does. Something appears to be blocking the Homesharing between my PC and the AppleTV even though the Apple TV is successfully connected to my home network. I spoke with an Apple Support Tech who was unable to help me becuase I have a PC! He admitted this is a common problem with FIOS and PCS. There must be a port that needs to be opened in the router. I do not beleive it is anything to do with my antivirus software or Windows Defender as i uninstalled all and still not communication. Must be a port within the routter that is blocking tis communication. On my Itunes you can see that it does not see the Apple TV. Please advise.

I'd have to agree. I set my vms and two clients on Saturday in one hour. I think the picture is better I did not see an issue with the brightness. For the heck of it I recorded five channels at once to test it. I've also noticed when playing a recorded show on the client everything responds a lot quicker. So I am impressed and curious to see what new features come later.
Kudos to verizon.

Windows Update on VMs seems to only work one at a time

I have a handful of Win 2012 R2 VMs (running on ESXi) I've inherited. I've tried 3 or 4 times to update them now since taking them
over, and noticed the strangest thing - only one of them will download updates at a time. If I start the update on all of them, the others will just hang at 0%. A little while after one finishes, another one will finally start to download. I'm completely stumped
as to why/how this could be happening. Is this even possible, or just an incredibly strange coincidence? Is there anything I can check to prove one way or the other? I'm wondering if it's something odd like they were all cloned from one base VM in some odd
way such that WU is seeing them as the same server when they try to connect or something... Other computers can connect to WU while this is happening; it's just this little cluster of VMs that were all built together.

Hi Allison,
Just addition. Did you check if those problematic VMs can access internet at the same time? For example, can
those VMs browser any webpage successfully at the same time, not just download updates? Meanwhile, please check if there has policies on router ports to limit the number of MAC addresses per port.
Hope this helps.
Best regards,
Justin Gu

VMS port of BerkeleyDB

Similar Messages

Maybe you are looking for