G41M-P23 - Wrong type of memory?

I recently bought a G41M-P23 motherboard, a Intel E3400 and two sticks of 2GB Kingmax RAM DRR3 1333MHz. The RAM appears to be running well at 1066MHz, however the overall system is unstable.
Could the fact that the frequencies don't match up affect the system stability? According to MSI this motherboard can support RAM running at 1333MHz in an OC mode. Can I OC the RAM without stressing the CPU too much?

Quote
however the overall system is unstable.
Can you please be more specific about the issue or issues your are actually facing? Please define "the overall system is unstable" in terms of the most common symptoms.
Also, please provide full system specifications: >>Posting Guide<<
Quote
Could the fact that the frequencies don't match up affect the system stability?
What frequencies are you referring to exactly?
Quote
According to MSI this motherboard can support RAM running at 1333MHz in an OC mode. Can I OC the RAM without stressing the CPU too much?
It is not the mainboard that is "causing" this limitation into existance but the Chipset (or to be more precise: its memory controller). According to Intel specifications it natively supports DDR3-800 and DDR3-1066 memory modules. Everything faster than that means overclocking the memory controller/memory bus.
Quote
without stressing the CPU
Overclocking your memory is not directly related to your processor or its frequency. If you already have stability problems @DDR3-1066, then overclocking the memory/memory bus (or actually: overclocking as such) is probably the last thing your should engage in at the moment.

Similar Messages

MOVED: G41M-P23 - Wrong type of memory?

This topic has been moved to Intel Core 2 Duo/Quad boards.
https://forum-en.msi.com/index.php?topic=148353.0

Quote
however the overall system is unstable.
Can you please be more specific about the issue or issues your are actually facing? Please define "the overall system is unstable" in terms of the most common symptoms.
Also, please provide full system specifications: >>Posting Guide<<
Quote
Could the fact that the frequencies don't match up affect the system stability?
What frequencies are you referring to exactly?
Quote
According to MSI this motherboard can support RAM running at 1333MHz in an OC mode. Can I OC the RAM without stressing the CPU too much?
It is not the mainboard that is "causing" this limitation into existance but the Chipset (or to be more precise: its memory controller). According to Intel specifications it natively supports DDR3-800 and DDR3-1066 memory modules. Everything faster than that means overclocking the memory controller/memory bus.
Quote
without stressing the CPU
Overclocking your memory is not directly related to your processor or its frequency. If you already have stability problems @DDR3-1066, then overclocking the memory/memory bus (or actually: overclocking as such) is probably the last thing your should engage in at the moment.

ORA-30012: undo tablespace 'UNDOTBS' does not exist or of wrong type

OS Version : AIX 6.1
DB Version : 11.2.0.1
I am duplicating database and got below error:
contents of Memory Script:
   Alter clone database open resetlogs;
executing Memory Script
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03004: fatal error during execution of command
RMAN-10041: Could not re-create polling channel context following failure.
RMAN-10024: error setting up for rpc polling
RMAN-10005: error opening cursor
RMAN-10002: ORACLE error: ORA-03114: not connected to ORACLE
RMAN-03002: failure of Duplicate Db command at 02/16/2013 17:20:02
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: ORACLE error from auxiliary database: ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-30012: undo tablespace 'UNDOTBS' does not exist or of wrong type
Process ID: 44040326
Session ID: 65 Serial number: 3
Error is because in target database undo tablespace is UNDOTBS_NEW and in auxiliary database undo tablespace name in init file is UNDOTBS. I followed the meatlink doc 433992.1 which suggest following steps to recover from above error:
1) edit the parameter UNDO_MANAGEMENT to "MANUAL"
2) start database again
3) drop the UNDO tablespace
4) recreate UNDO tablespace which matches to name in init file.
5) shutdown & start DB again.
Now, i edited init file and tried to start DB and got following error:
oracore@cph-core-db01-s $ sqlplus /nolog
SQL*Plus: Release 11.2.0.1.0 Production on Sat Feb 16 17:22:11 2013
Copyright (c) 1982, 2009, Oracle. All rights reserved.
SQL> conn sys as sysdba
Enter password:
Connected to an idle instance.
SQL> startup
ORACLE instance started.
Total System Global Area 4275781632 bytes
Fixed Size                  2213632 bytes
Variable Size             822085888 bytes
Database Buffers         3439329280 bytes
Redo Buffers               12152832 bytes
Database mounted.
ORA-01113: file 1 needs media recovery
ORA-01110: data file 1: '/u04/oradata/CORE/CORE_DUP/system01.dbf'I don't want to run duplicate command with correct UNDO tablespace name. Any other work around for this ?

STARTUP MOUNT
RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL
CANCEL
ALTER DATABASE OPEN RESETLOGS
Above option is not working for CORE_DUP, i am getting very strange error, while trying to recover i am getting very strange error as below:
oracore@cph-core-db01-s $ export ORACLE_SID=CORE_DUP
SQL*Plus: Release 11.2.0.1.0 Production on Mon Feb 18 11:17:25 2013
Copyright (c) 1982, 2009, Oracle. All rights reserved.
SQL> conn sys as sysdba
Enter password:
Connected to an idle instance.
SQL> startup mount
ORACLE instance started.
Total System Global Area 4275781632 bytes
Fixed Size                  2213632 bytes
Variable Size             822085888 bytes
Database Buffers         3439329280 bytes
Redo Buffers               12152832 bytes
Database mounted.
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01139: RESETLOGS option only valid after an incomplete database recovery
SQL> recover database using backup controlfile until cancel;
ORA-00283: recovery session canceled due to errors
ORA-16433: The database must be opened in read/write mode.Primary database initfile:
event="10298 trace name context forever, level 32"
db_block_size=8192
db_file_multiblock_read_count=16
open_cursors=300
db_name=CORE
cursor_sharing='SIMILAR'
global_names=FALSE
diagnostic_dest=/u01/app/oracore/diag/CORE
#background_dump_dest=/u01/app/oracore/diag/rdbms/bdump
#core_dump_dest=/u01/app/oracore/diag/rdbms/cdump
#user_dump_dest=/u01/app/oracore/diag/rdbms/udump
control_files=("/u01/oradata/CORE/control01.ctl", "/u02/oradata/CORE/control02.ctl", "/u03/oradata/CORE/control03.ctl")
log_archive_dest_1='LOCATION=/u05/oradata/CORE/'
log_archive_format='CORE_%s%t%r.ARC'
job_queue_processes=10
compatible=11.2.0.1
processes=150
fast_start_mttr_target=300
filesystemio_options='SETALL'
pga_aggregate_target=500M
recyclebin='OFF'
remote_login_passwordfile='EXCLUSIVE'
session_cached_cursors=100
sga_target=4G
undo_management='AUTO'
undo_tablespace='UNDOTBS_NEW'
nls_date_format='DD-MON-RRRR'
nls_length_semantics='CHAR'initfile for CORE_DUP
event="10298 trace name context forever, level 32"
db_block_size=8192
db_file_multiblock_read_count=16
open_cursors=300
db_name=CORE_DUP
cursor_sharing='SIMILAR'
global_names=FALSE
diagnostic_dest=/u01/app/oracore/diag/CORE/CORE_DUP
control_files=("/u01/oradata/CORE/CORE_DUP/control01.ctl", "/u02/oradata/CORE/CORE_DUP/control02.ctl", "/u03/oradata/CORE/CORE_DUP/control03.ctl")
log_archive_dest_1='LOCATION=/u05/oradata/CORE/CORE_DUP/'
log_archive_format='CORE_DUP%s%t%r.ARC'
job_queue_processes=10
compatible=11.2.0.1
_compression_compatibility="11.2.0"
processes=150
fast_start_mttr_target=300
filesystemio_options='SETALL'
pga_aggregate_target=500M
recyclebin='OFF'
remote_login_passwordfile='EXCLUSIVE'
session_cached_cursors=100
sga_target=4G
undo_management='AUTO'
undo_tablespace='UNDOTBS'
nls_date_format='DD-MON-RRRR'
nls_length_semantics='CHAR'
log_file_name_convert='/CORE','/CORE/CORE_DUP'
db_file_name_convert='/CORE','/CORE/CORE_DUP'Duplicate steps are as:
oracore@cph-core-db01-s $ rman target sys/zzzz@core catalog rmantst10/zzzzz@catdb auxiliary /
Recovery Manager: Release 11.2.0.1.0 - Production on Mon Feb 18 15:50:00 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: CORE (DBID=913972022)
connected to recovery catalog database
connected to auxiliary database: CORE_DUP (not mounted)
RMAN> duplicate target database to CORE_DUP;
Starting Duplicate Db at 18-FEB-13
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=96 device type=DISK
allocated channel: ORA_AUX_DISK_2
channel ORA_AUX_DISK_2: SID=127 device type=DISK
contents of Memory Script:
   sql clone "create spfile from memory";
executing Memory Script
sql statement: create spfile from memory
contents of Memory Script:
   shutdown clone immediate;
   startup clone nomount;
executing Memory Script
Oracle instance shut down
connected to auxiliary database (not started)
Oracle instance started
Total System Global Area    4275781632 bytes
Fixed Size                     2213632 bytes
Variable Size                838863104 bytes
Database Buffers            3422552064 bytes
Redo Buffers                  12152832 bytes
contents of Memory Script:
   sql clone "alter system set db_name =
''CORE'' comment=
''Modified by RMAN duplicate'' scope=spfile";
   sql clone "alter system set db_unique_name =
''CORE_DUP'' comment=
''Modified by RMAN duplicate'' scope=spfile";
   shutdown clone immediate;
   startup clone force nomount
   restore clone primary controlfile;
   alter clone database mount;
executing Memory Script
sql statement: alter system set db_name = ''CORE'' comment= ''Modified by RMAN duplicate'' scope=spfile
sql statement: alter system set db_unique_name = ''CORE_DUP'' comment= ''Modified by RMAN duplicate'' scope=spfile
Oracle instance shut down
Oracle instance started
Total System Global Area    4275781632 bytes
Fixed Size                     2213632 bytes
Variable Size                838863104 bytes
Database Buffers            3422552064 bytes
Redo Buffers                  12152832 bytes
Starting restore at 18-FEB-13
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=96 device type=DISK
allocated channel: ORA_AUX_DISK_2
channel ORA_AUX_DISK_2: SID=127 device type=DISK
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: reading from backup piece /oraclebackup/CORE/DF_L1_CORE_16022013_5fo246k3_175_1
channel ORA_AUX_DISK_1: piece handle=/oraclebackup/CORE/DF_L1_CORE_16022013_5fo246k3_175_1 tag=LEVEL1
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:03
output file name=/u01/oradata/CORE/CORE_DUP/control01.ctl
output file name=/u02/oradata/CORE/CORE_DUP/control02.ctl
output file name=/u03/oradata/CORE/CORE_DUP/control03.ctl
Finished restore at 18-FEB-13
database mounted
contents of Memory Script:
   set until scn 1217601;
   set newname for datafile 1 to
"/u04/oradata/CORE/CORE_DUP/system01.dbf";
   set newname for datafile 2 to
"/u04/oradata/CORE/CORE_DUP/sysaux01.dbf";
   set newname for datafile 4 to
"/u04/oradata/CORE/CORE_DUP/users01.dbf";
   set newname for datafile 5 to
"/u04/oradata/CORE/CORE_DUP/users02.dbf";
   set newname for datafile 6 to
"/u04/oradata/CORE/CORE_DUP/users03.dbf";
   set newname for datafile 9 to
"/u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf";
   restore
   clone database
executing Memory Script
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 18-FEB-13
using channel ORA_AUX_DISK_1
using channel ORA_AUX_DISK_2
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_1: restoring datafile 00004 to /u04/oradata/CORE/CORE_DUP/users01.dbf
channel ORA_AUX_DISK_1: restoring datafile 00005 to /u04/oradata/CORE/CORE_DUP/users02.dbf
channel ORA_AUX_DISK_1: restoring datafile 00006 to /u04/oradata/CORE/CORE_DUP/users03.dbf
channel ORA_AUX_DISK_1: reading from backup piece /oraclebackup/CORE/DF_L0_CORE_16022013_55o246fe_165_1
channel ORA_AUX_DISK_2: starting datafile backup set restore
channel ORA_AUX_DISK_2: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_2: restoring datafile 00001 to /u04/oradata/CORE/CORE_DUP/system01.dbf
channel ORA_AUX_DISK_2: restoring datafile 00002 to /u04/oradata/CORE/CORE_DUP/sysaux01.dbf
channel ORA_AUX_DISK_2: restoring datafile 00009 to /u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf
channel ORA_AUX_DISK_2: reading from backup piece /oraclebackup/CORE/DF_L0_CORE_16022013_56o246fe_166_1
channel ORA_AUX_DISK_2: piece handle=/oraclebackup/CORE/DF_L0_CORE_16022013_56o246fe_166_1 tag=LEVEL0
channel ORA_AUX_DISK_2: restored backup piece 1
channel ORA_AUX_DISK_2: restore complete, elapsed time: 00:01:15
channel ORA_AUX_DISK_1: piece handle=/oraclebackup/CORE/DF_L0_CORE_16022013_55o246fe_165_1 tag=LEVEL0
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:01:35
Finished restore at 18-FEB-13
contents of Memory Script:
   switch clone datafile all;
executing Memory Script
datafile 1 switched to datafile copy
input datafile copy RECID=24 STAMP=807724355 file name=/u04/oradata/CORE/CORE_DUP/system01.dbf
datafile 2 switched to datafile copy
input datafile copy RECID=25 STAMP=807724355 file name=/u04/oradata/CORE/CORE_DUP/sysaux01.dbf
datafile 4 switched to datafile copy
input datafile copy RECID=26 STAMP=807724356 file name=/u04/oradata/CORE/CORE_DUP/users01.dbf
datafile 5 switched to datafile copy
input datafile copy RECID=27 STAMP=807724356 file name=/u04/oradata/CORE/CORE_DUP/users02.dbf
datafile 6 switched to datafile copy
input datafile copy RECID=28 STAMP=807724356 file name=/u04/oradata/CORE/CORE_DUP/users03.dbf
datafile 9 switched to datafile copy
input datafile copy RECID=29 STAMP=807724356 file name=/u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf
contents of Memory Script:
   set until scn 1217601;
   recover
   clone database
    delete archivelog
executing Memory Script
executing command: SET until clause
Starting recover at 18-FEB-13
using channel ORA_AUX_DISK_1
using channel ORA_AUX_DISK_2
channel ORA_AUX_DISK_1: starting incremental datafile backup set restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
destination for restore of datafile 00001: /u04/oradata/CORE/CORE_DUP/system01.dbf
destination for restore of datafile 00002: /u04/oradata/CORE/CORE_DUP/sysaux01.dbf
destination for restore of datafile 00009: /u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf
channel ORA_AUX_DISK_1: reading from backup piece /oraclebackup/CORE/DF_L1_CORE_16022013_5eo246k2_174_1
channel ORA_AUX_DISK_2: starting incremental datafile backup set restore
channel ORA_AUX_DISK_2: specifying datafile(s) to restore from backup set
destination for restore of datafile 00004: /u04/oradata/CORE/CORE_DUP/users01.dbf
destination for restore of datafile 00005: /u04/oradata/CORE/CORE_DUP/users02.dbf
destination for restore of datafile 00006: /u04/oradata/CORE/CORE_DUP/users03.dbf
channel ORA_AUX_DISK_2: reading from backup piece /oraclebackup/CORE/DF_L1_CORE_16022013_5do246k2_173_1
channel ORA_AUX_DISK_1: piece handle=/oraclebackup/CORE/DF_L1_CORE_16022013_5eo246k2_174_1 tag=LEVEL1
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
channel ORA_AUX_DISK_2: piece handle=/oraclebackup/CORE/DF_L1_CORE_16022013_5do246k2_173_1 tag=LEVEL1
channel ORA_AUX_DISK_2: restored backup piece 1
channel ORA_AUX_DISK_2: restore complete, elapsed time: 00:00:01
starting media recovery
archived log for thread 1 with sequence 1718 is already on disk as file /u05/oradata/CORE/CORE_17181807276264.ARC
archived log for thread 1 with sequence 1719 is already on disk as file /u05/oradata/CORE/CORE_17191807276264.ARC
archived log for thread 1 with sequence 1720 is already on disk as file /u05/oradata/CORE/CORE_17201807276264.ARC
archived log for thread 1 with sequence 1721 is already on disk as file /u05/oradata/CORE/CORE_17211807276264.ARC
archived log for thread 1 with sequence 1722 is already on disk as file /u05/oradata/CORE/CORE_17221807276264.ARC
archived log for thread 1 with sequence 1723 is already on disk as file /u05/oradata/CORE/CORE_17231807276264.ARC
archived log for thread 1 with sequence 1724 is already on disk as file /u05/oradata/CORE/CORE_17241807276264.ARC
archived log for thread 1 with sequence 1725 is already on disk as file /u05/oradata/CORE/CORE_17251807276264.ARC
archived log for thread 1 with sequence 1726 is already on disk as file /u05/oradata/CORE/CORE_17261807276264.ARC
archived log for thread 1 with sequence 1727 is already on disk as file /u05/oradata/CORE/CORE_17271807276264.ARC
archived log for thread 1 with sequence 1728 is already on disk as file /u05/oradata/CORE/CORE_17281807276264.ARC
archived log for thread 1 with sequence 1729 is already on disk as file /u05/oradata/CORE/CORE_17291807276264.ARC
archived log for thread 1 with sequence 1730 is already on disk as file /u05/oradata/CORE/CORE_17301807276264.ARC
archived log for thread 1 with sequence 1731 is already on disk as file /u05/oradata/CORE/CORE_17311807276264.ARC
archived log for thread 1 with sequence 1732 is already on disk as file /u05/oradata/CORE/CORE_17321807276264.ARC
archived log for thread 1 with sequence 1733 is already on disk as file /u05/oradata/CORE/CORE_17331807276264.ARC
archived log for thread 1 with sequence 1734 is already on disk as file /u05/oradata/CORE/CORE_17341807276264.ARC
archived log for thread 1 with sequence 1735 is already on disk as file /u05/oradata/CORE/CORE_17351807276264.ARC
archived log for thread 1 with sequence 1736 is already on disk as file /u05/oradata/CORE/CORE_17361807276264.ARC
archived log for thread 1 with sequence 1737 is already on disk as file /u05/oradata/CORE/CORE_17371807276264.ARC
archived log for thread 1 with sequence 1738 is already on disk as file /u05/oradata/CORE/CORE_17381807276264.ARC
archived log for thread 1 with sequence 1739 is already on disk as file /u05/oradata/CORE/CORE_17391807276264.ARC
archived log for thread 1 with sequence 1740 is already on disk as file /u05/oradata/CORE/CORE_17401807276264.ARC
archived log for thread 1 with sequence 1741 is already on disk as file /u05/oradata/CORE/CORE_17411807276264.ARC
archived log for thread 1 with sequence 1742 is already on disk as file /u05/oradata/CORE/CORE_17421807276264.ARC
archived log for thread 1 with sequence 1743 is already on disk as file /u05/oradata/CORE/CORE_17431807276264.ARC
archived log for thread 1 with sequence 1744 is already on disk as file /u05/oradata/CORE/CORE_17441807276264.ARC
channel ORA_AUX_DISK_1: starting archived log restore to default destination
channel ORA_AUX_DISK_1: restoring archived log
archived log thread=1 sequence=1710
channel ORA_AUX_DISK_1: reading from backup piece /oraclebackup/CORE/ARC_1HR_CORE_16022013_5jo24jp8_179_1
channel ORA_AUX_DISK_2: starting archived log restore to default destination
channel ORA_AUX_DISK_2: restoring archived log
archived log thread=1 sequence=1711
channel ORA_AUX_DISK_2: restoring archived log
archived log thread=1 sequence=1712
channel ORA_AUX_DISK_2: restoring archived log
archived log thread=1 sequence=1713
channel ORA_AUX_DISK_2: restoring archived log
archived log thread=1 sequence=1714
channel ORA_AUX_DISK_2: restoring archived log
archived log thread=1 sequence=1715
channel ORA_AUX_DISK_2: restoring archived log
archived log thread=1 sequence=1716
channel ORA_AUX_DISK_2: restoring archived log
archived log thread=1 sequence=1717
channel ORA_AUX_DISK_2: reading from backup piece /oraclebackup/CORE/ARC_1HR_CORE_18022013_5ko296uf_180_1
channel ORA_AUX_DISK_1: piece handle=/oraclebackup/CORE/ARC_1HR_CORE_16022013_5jo24jp8_179_1 tag=ARC_1HR
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17101807276264.ARC thread=1 sequence=1710
channel clone_default: deleting archived log(s)
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17101807276264.ARC RECID=3041 STAMP=807724360
channel ORA_AUX_DISK_2: piece handle=/oraclebackup/CORE/ARC_1HR_CORE_18022013_5ko296uf_180_1 tag=ARC_1HR
channel ORA_AUX_DISK_2: restored backup piece 1
channel ORA_AUX_DISK_2: restore complete, elapsed time: 00:00:08
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17111807276264.ARC thread=1 sequence=1711
channel clone_default: deleting archived log(s)
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17111807276264.ARC RECID=3042 STAMP=807724362
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17121807276264.ARC thread=1 sequence=1712
channel clone_default: deleting archived log(s)
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17121807276264.ARC RECID=3043 STAMP=807724363
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17131807276264.ARC thread=1 sequence=1713
channel clone_default: deleting archived log(s)
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17131807276264.ARC RECID=3044 STAMP=807724367
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17141807276264.ARC thread=1 sequence=1714
channel clone_default: deleting archived log(s)
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17141807276264.ARC RECID=3048 STAMP=807724367
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17151807276264.ARC thread=1 sequence=1715
channel clone_default: deleting archived log(s)
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17151807276264.ARC RECID=3046 STAMP=807724367
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17161807276264.ARC thread=1 sequence=1716
channel clone_default: deleting archived log(s)
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17161807276264.ARC RECID=3045 STAMP=807724367
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17171807276264.ARC thread=1 sequence=1717
channel clone_default: deleting archived log(s)
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17171807276264.ARC RECID=3047 STAMP=807724367
archived log file name=/u05/oradata/CORE/CORE_17181807276264.ARC thread=1 sequence=1718
archived log file name=/u05/oradata/CORE/CORE_17191807276264.ARC thread=1 sequence=1719
archived log file name=/u05/oradata/CORE/CORE_17201807276264.ARC thread=1 sequence=1720
archived log file name=/u05/oradata/CORE/CORE_17211807276264.ARC thread=1 sequence=1721
archived log file name=/u05/oradata/CORE/CORE_17221807276264.ARC thread=1 sequence=1722
archived log file name=/u05/oradata/CORE/CORE_17231807276264.ARC thread=1 sequence=1723
archived log file name=/u05/oradata/CORE/CORE_17241807276264.ARC thread=1 sequence=1724
archived log file name=/u05/oradata/CORE/CORE_17251807276264.ARC thread=1 sequence=1725
archived log file name=/u05/oradata/CORE/CORE_17261807276264.ARC thread=1 sequence=1726
archived log file name=/u05/oradata/CORE/CORE_17271807276264.ARC thread=1 sequence=1727
archived log file name=/u05/oradata/CORE/CORE_17281807276264.ARC thread=1 sequence=1728
archived log file name=/u05/oradata/CORE/CORE_17291807276264.ARC thread=1 sequence=1729
archived log file name=/u05/oradata/CORE/CORE_17301807276264.ARC thread=1 sequence=1730
archived log file name=/u05/oradata/CORE/CORE_17311807276264.ARC thread=1 sequence=1731
archived log file name=/u05/oradata/CORE/CORE_17321807276264.ARC thread=1 sequence=1732
archived log file name=/u05/oradata/CORE/CORE_17331807276264.ARC thread=1 sequence=1733
archived log file name=/u05/oradata/CORE/CORE_17341807276264.ARC thread=1 sequence=1734
archived log file name=/u05/oradata/CORE/CORE_17351807276264.ARC thread=1 sequence=1735
archived log file name=/u05/oradata/CORE/CORE_17361807276264.ARC thread=1 sequence=1736
archived log file name=/u05/oradata/CORE/CORE_17371807276264.ARC thread=1 sequence=1737
archived log file name=/u05/oradata/CORE/CORE_17381807276264.ARC thread=1 sequence=1738
archived log file name=/u05/oradata/CORE/CORE_17391807276264.ARC thread=1 sequence=1739
archived log file name=/u05/oradata/CORE/CORE_17401807276264.ARC thread=1 sequence=1740
archived log file name=/u05/oradata/CORE/CORE_17411807276264.ARC thread=1 sequence=1741
archived log file name=/u05/oradata/CORE/CORE_17421807276264.ARC thread=1 sequence=1742
archived log file name=/u05/oradata/CORE/CORE_17431807276264.ARC thread=1 sequence=1743
archived log file name=/u05/oradata/CORE/CORE_17441807276264.ARC thread=1 sequence=1744
media recovery complete, elapsed time: 00:00:33
Finished recover at 18-FEB-13
contents of Memory Script:
   shutdown clone immediate;
   startup clone nomount;
   sql clone "alter system set db_name =
''CORE_DUP'' comment=
''Reset to original value by RMAN'' scope=spfile";
   sql clone "alter system reset db_unique_name scope=spfile";
   shutdown clone immediate;
   startup clone nomount;
executing Memory Script
database dismounted
Oracle instance shut down
connected to auxiliary database (not started)
Oracle instance started
Total System Global Area    4275781632 bytes
Fixed Size                     2213632 bytes
Variable Size                838863104 bytes
Database Buffers            3422552064 bytes
Redo Buffers                  12152832 bytes
sql statement: alter system set db_name = ''CORE_DUP'' comment= ''Reset to original value by RMAN'' scope=spfile
sql statement: alter system reset db_unique_name scope=spfile
Oracle instance shut down
connected to auxiliary database (not started)
Oracle instance started
Total System Global Area    4275781632 bytes
Fixed Size                     2213632 bytes
Variable Size                838863104 bytes
Database Buffers            3422552064 bytes
Redo Buffers                  12152832 bytes
sql statement: CREATE CONTROLFILE REUSE SET DATABASE "CORE_DUP" RESETLOGS ARCHIVELOG
MAXLOGFILES     32
MAXLOGMEMBERS      4
MAXDATAFILES      500
MAXINSTANCES     1
MAXLOGHISTORY     2298
LOGFILE
GROUP 1 ( '/u02/oradata/CORE/CORE_DUP/redo01a.log', '/u03/oradata/CORE/CORE_DUP/redo01b.log' ) SIZE 10 M REUSE,
GROUP 2 ( '/u02/oradata/CORE/CORE_DUP/redo02a.log', '/u03/oradata/CORE/CORE_DUP/redo02b.log' ) SIZE 10 M REUSE,
GROUP 3 ( '/u02/oradata/CORE/CORE_DUP/redo03a.log', '/u03/oradata/CORE/CORE_DUP/redo03b.log' ) SIZE 10 M REUSE
DATAFILE
'/u04/oradata/CORE/CORE_DUP/system01.dbf'
CHARACTER SET AL32UTF8
contents of Memory Script:
   set newname for tempfile 1 to
"/u04/oradata/CORE/CORE_DUP/temp01.dbf";
   switch clone tempfile all;
   catalog clone datafilecopy "/u04/oradata/CORE/CORE_DUP/sysaux01.dbf",
"/u04/oradata/CORE/CORE_DUP/users01.dbf",
"/u04/oradata/CORE/CORE_DUP/users02.dbf",
"/u04/oradata/CORE/CORE_DUP/users03.dbf",
"/u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf";
   switch clone datafile all;
executing Memory Script
executing command: SET NEWNAME
renamed tempfile 1 to /u04/oradata/CORE/CORE_DUP/temp01.dbf in control file
cataloged datafile copy
datafile copy file name=/u04/oradata/CORE/CORE_DUP/sysaux01.dbf RECID=1 STAMP=807724423
cataloged datafile copy
datafile copy file name=/u04/oradata/CORE/CORE_DUP/users01.dbf RECID=2 STAMP=807724423
cataloged datafile copy
datafile copy file name=/u04/oradata/CORE/CORE_DUP/users02.dbf RECID=3 STAMP=807724423
cataloged datafile copy
datafile copy file name=/u04/oradata/CORE/CORE_DUP/users03.dbf RECID=4 STAMP=807724423
cataloged datafile copy
datafile copy file name=/u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf RECID=5 STAMP=807724423
datafile 2 switched to datafile copy
input datafile copy RECID=1 STAMP=807724423 file name=/u04/oradata/CORE/CORE_DUP/sysaux01.dbf
datafile 4 switched to datafile copy
input datafile copy RECID=2 STAMP=807724423 file name=/u04/oradata/CORE/CORE_DUP/users01.dbf
datafile 5 switched to datafile copy
input datafile copy RECID=3 STAMP=807724423 file name=/u04/oradata/CORE/CORE_DUP/users02.dbf
datafile 6 switched to datafile copy
input datafile copy RECID=4 STAMP=807724423 file name=/u04/oradata/CORE/CORE_DUP/users03.dbf
datafile 9 switched to datafile copy
input datafile copy RECID=5 STAMP=807724423 file name=/u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf
contents of Memory Script:
   Alter clone database open resetlogs;
executing Memory Script
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03004: fatal error during execution of command
RMAN-10041: Could not re-create polling channel context following failure.
RMAN-10024: error setting up for rpc polling
RMAN-10005: error opening cursor
RMAN-10002: ORACLE error: ORA-03114: not connected to ORACLE
RMAN-03002: failure of Duplicate Db command at 02/18/2013 15:53:50
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: ORACLE error from auxiliary database: ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-30012: undo tablespace 'UNDOTBS' does not exist or of wrong type
Process ID: 3670170
Session ID: 33 Serial number: 7
oracore@cph-core-db01-s $

G41M-P23 & E2160 "stuck" at 315

First a disclaimer: I know next to nothing about what I'm doing here so be bear with me...
So I have a G41M-P23 motherboard and an E2160 that I'm trying to overclock. Have everything in BIOS either at default or auto (except Spread Spectrum is off and memory multiplier cranked down to keep memory speed around 800 until I find the CPU limits first). I can go to 315MHz & 2.84GHz just fine like this but after that I hit a strange wall. What I mean by that is that regardless of what I set BCLK to (320, 333 etc.) in reality it stays at 315.5MHz. BIOS reports CPU speed & BLCK as set (for example 333MHz & 3GHz) but everything else (CPU-Z, RealTemp etc.) says 315.5 & 2.84 when running full load with IntelBurn. Setting anything less than 315 produces expected results, it's just going above that when "things get stuck".
Just in case I reflashed BIOS (latest available for this MB) and also tried clearing CMOS & loading defaults but no change.
I'm probably doing some very basic mistake here but for the life of me I can't figure it out, any ideas?

Quote from: Bernhard on 05-May-11, 20:43:59
Just keep monitoring your CPU temps under load as you increase the CPU frequency.
I realize that E2160 & G41 are not exactly cutting edge and of interest to folks now-a-days, but in case anyone is interested I found that the earlier mentioned 350MHz was about far as I could go and have things stable (run IntelBurn over night without any problems). Increasing NB voltage (up to 1.23V) got me no further either. Just to be on the safe side, took things down a notch and settled for 345MHz which works OK with AUTO NB voltage.
Having settled that, I found that I can use multi 9 i.e. run CPU at 3.1GHz stable. This did require increasing Core voltage to 1.41V which I assume is a bit on the high side but should still be OK. The E2160 is L2 with VID 1.3250.
Running full load with IntelBurn core temps are, according to RealTemp, around 58-59 with peak at 61. CPU temp, according to MSI Overclocking Center, is around 52-53 with peak at 54. Again I assume that these should be acceptable.
Memory wise I found that anything over 1100MHz gets things very unstable, increasing memory voltage to 1.65V and relaxed timings did not not help. SPD on the memory says 1.5V and 9-9-9-24 @ 1333 (got these from a guy who considered these "junk"). Now running @ 1035 and 7-7-7-20. If my math is correct, I think I could take RAS down to 19 even within the SPD spec.
So unless someone says that 1.41V is way too much or that those temps are way over the top, I think I'll call it a day. I don't doubt this could run faster but I suspect that from here on it would be "diminishing returns for increasing amount of work".
Once more, thanks for your help!

MSI G41M-P23 FSB/core clock issue (HELP!)

Alright, so a few days ago I bought an MSI G41M-P23 with 8 gb of DDR3 1066 (PC3 8500) RAM (the standard for this board). My CPU is an E8400 (3.0 ghz). At first I wanted to maybe fiddle with some overclocking, which is where I realized that this mobo fails at. Not a big deal...but every time I attempted to up the FSB above 336 or so (this CPU's default is 333... x 9 = 3000 mhz), the system would not POST, instead it simply would loop on/off until eventually going back to defaults.
That was fine with me -- I don't need to overclock, really. However, I noticed something odd in the BIOS. The CPU speed, which according to the fsb multiplier was the correct speed (2997 mhz), was very not correct in the CPU info section of the BIOS. There, it listed the speed at 1.8 ghz. Thus I decided, for the heck of it, to take at look at CPU-Z at this time.
This is what CPU-Z is currently telling me (I have a screenshot, but I can't seem to post it here):
In the "Clocks" section (bottom left of the main tab in CPU-Z)
Core speed: ~1894 mhz
Multiplier: x 9.0
Bus Speed: ~210 mhz
Rated FSB: ~842 mhz
The RAM speeds and ratios are correct, though, given the FSB:RAM ratio (it would seem). Ram clocks in at ~333 mhz, which with a 5:8 ratio should put it at 1066...I think.
So now CPU-Z and part(?) of the BIOS is showing me the wrong CPU speed (1800 mhz). It's also listing my FSB at 200 mhz despite the fact that my I set it in my BIOS at 333 mhz. The 200 Mhz adds up with the incorrect core speed, as 200 X 9 = 1800. If I go back to the BIOS, it lists the FSB correctly, and the POST screen displays the correct FSB and multiplier, but again, the CPU info screen of the bios is reading 1800 mhz, while listing the FSB as 333. I don't have any speedstep/CE1/other modifiers turned on, and this reading is currently under normal load (read: not idle). I'm at my wit's end here.
Is this board not saving my FSB speeds in the BIOS? Is there any way to fix this issue? I apparently have the most up-to-date BIOS according to CPU-Z and MSI's support website. I have not tried every setting of the OC switch yet, though I have tried a few (200 -> 333, for example) and all have resulted in a system that will not POST, and leaves me having to reset the CMOS jumper in order to get it to boot again (as opposed to the looping/defaulting cycle mentioned earlier).
Can someone PLEASE help me? I just reinstalled Windows 7 x64/all my programs because of this new board...and I really, really don't want to do that all again.

Well, I heard back from MSI. They are just as confused over the BIOS version as I am, apparently. V30.8 is not what is supposed to be on the board. So, rather than flash it and hope that it works, etc., I decided to simply return the board, as I've only had it for a few days, and bared used it. Something is clearly wrong with it to have an "unknown" BIOS installed.
I went ahead and ordered a new CPU and mobo entirely...Core i5, too. No MSI board this time...only because they didn't have a board in my price range. I wanted this upgrade to be something easy and simple so I wouldn't have to do that.. oh well.
I do find it very strange what's happened with this board, though....I've never before heard of ordering and receiving a board with an unknown BIOS on it...even according to the manufacturer. Maybe an out-of-date BIOS, but not something completely off the radar. Still, thank you again for your help.

'expression is of wrong type' - but which and where..?

hello.
Hopefully this will be clear as day to someone.. Please could someone tell me why I'm getting the following error message..
[061010_042222995][][EXCEPTION] SQLException encounter while executing data trigger....
java.sql.SQLException: ORA-06550: line 4, column 20:
PLS-00382: expression is of wrong type
ORA-06550: line 4, column 1:
PL/SQL: Statement ignoreddata template where trigger is called..
<?xml version="1.0" encoding="utf-8" ?>
- <dataTemplate name="UofS_OutstandngExpenses_Report" defaultPackage="SUBIXCLT" dataSourceRef="FINDEV" version="1.0">
- <properties>
<property name="xml_tag_case" value="upper" />
<property name="include_parameters" value="true" />
<property name="debug_mode" value="on" />
</properties>
- <parameters>
<parameter name="p_claimant" dataType="character" defaultValue="" />
<parameter name="p_expense_date_from" dataType="date" defaultValue="" />
<parameter name="p_expense_date_to" dataType="date" defaultValue="" />
<parameter name="p_raisedby" dataType="character" defaultValue="" />
<parameter name="p_status" dataType="character" defaultValue="" />
<parameter name="p_ordered_by" dataType="varchar2" defaultValue="" />
</parameters>
- <dataQuery>
- <sqlStatement name="Q1">
- <![CDATA[
SELECT DISTINCT
erh.invoice_num,
pap.full_name EMP_CLAIMING,
DECODE(NVL(erh.expense_status_code, 'Not yet Submitted (NULL)'), 'CANCELLED', 'CANCELLED',
     'EMPAPPR', 'Pending Individuals Approval',      'ERROR', 'Pending System Administrator Action',
     'HOLD_PENDING_RECEIPTS     ', 'Hold Pending Receipts', 'INPROGRESS', 'In Progress', 'INVOICED', 'Ready for Payment',
     'MGRAPPR', 'Pending Payables Approval', 'MGRPAYAPPR', 'Ready for Invoicing', 'PAID', 'Paid',
     'PARPAID', 'Partially Paid',     'PAYAPPR', 'Payables Approved',     'PENDMGR', 'Pending Manager Approval',
     'PEND_HOLDS_CLEARANCE', 'Pending Payment Verification',     'REJECTED', 'Rejected',     'RESOLUTN',     'Pending Your Resolution',
     'RETURNED',     'Returned',     'SAVED',     'Saved',     'SUBMITTED',     'Submitted',     'UNUSED',     'UNUSED',
     'WITHDRAWN','Withdrawn',     'Not yet Submitted (NULL)') "EXPENSE_STATUS" ,
NVL(TO_CHAR(erh.report_submitted_date,'dd-MON-yyyy'),'NULL') SUBMIT_DATE,
NVL(TO_CHAR(erh.expense_last_status_date,'dd-MON-yyyy'),'NULL') LAST_UPDATE,
erh.override_approver_name ER_Approver,
fu.description EXP_ADMIN,
erh.total,
erh.description
FROM
AP_EXPENSE_REPORT_HEADERS_all erh,
per_all_people_f pap, fnd_user fu
WHERE erh.employee_id = pap.person_id
AND fu.user_id = erh.created_by
AND NVL(erh.expense_status_code, 'Not yet Submitted') NOT IN ('MGRAPPR', 'INVOICED', 'PAID', 'PARPAID')
AND pap.full_name = NVL(:p_claimant, pap.full_name)
AND TRUNC(erh.report_submitted_date) BETWEEN NVL(:p_expense_date_from, '01-JAN-1999') AND NVL(:p_expense_date_to,'31-DEC-2299')
AND fu.description = NVL(:p_raisedby,fu.description)
AND erh.expense_status_code = NVL(:p_status,erh.expense_status_code) &L_ORDERED_BY
]]>
</sqlStatement>
</dataQuery>
<dataTrigger name="beforeReport" source="SUBIXCLT.beforeReportTrigger" />
- <dataStructure>
- <group name="G_XP_CLM_TRACKNG" source="Q1">
<element name="INVOICE_NUM" value="INVOICE_NUM" />
<element name="EMP_CLAIMING" value="EMP_CLAIMING" />
<element name="EXPENSE_STATUS" value="EXPENSE_STATUS" />
<element name="SUBMIT_DATE" value="SUBMIT_DATE" />
<element name="LAST_UPDATE" value="LAST_UPDATE" />
</group>
</dataStructure>
</dataTemplate>and the package spec & body..
--THE SPEC...
CREATE OR REPLACE PACKAGE Subixclt IS
FUNCTION beforeReportTrigger RETURN VARCHAR2;
p_order_by VARCHAR2(50);
l_ordered_by VARCHAR2(350);
p_claimant VARCHAR2(80);
expense_date_from DATE;
expense_date_to DATE;
p_raisedby   VARCHAR2(80);
p_status   VARCHAR2(80);
p_ordered_by   VARCHAR2(80);
--RETURN VARCHAR2;
END;
--THE BODY...
REATE OR REPLACE PACKAGE BODY Subixclt IS
FUNCTION BeforeReportTrigger RETURN VARCHAR2 IS
BEGIN
Fnd_File.PUT_LINE(Fnd_File.LOG,'L_ORDERED_by'||L_ORDERED_BY);
DECLARE
L_ORDERED_BY VARCHAR2(50);
P_ORDERED_BY VARCHAR2(50);
P_RAISEDBY VARCHAR2(50);
P_STATUS VARCHAR2(50);
P_CLAIMANT VARCHAR2(100);
P_EXPENSE_DATE_FROM DATE;
--P_EXPENSE_DATE_FROM VARCHAR2(50);
--P_EXPENSE_DATE_TO VARCHAR2(50);
P_EXPENSE_DATE_TO DATE;
BEGIN
IF (P_ORDERED_BY='Expense Report Number') THEN
     L_ORDERED_BY :='order by 1 asc;';
ELSIF (P_ORDERED_BY='Person Claiming') THEN
     L_ORDERED_BY :='order by 2 asc;';
ELSIF (P_ORDERED_BY='Submit Date') THEN
L_ORDERED_BY :='order by 4 asc;';
END IF;
RETURN(L_ORDERED_BY);
--RETURN NULL;
END;
END;
END;Many thanks for looking..
D

Thanks for the suggestion. I initially didnt have the RETURN TRUE after every IF statement and have since removed the 'WHEN OTHERS' section but I'm still getting the same error message. If its to be believed, doesn't it sound like its not finding any of the 3 possible parameter entries available? This can't be so, I've checked the ConC Program parameter name is correct, and the value set linked to it only has available the 3 options where I make the choice..
Body now reads:
CREATE OR REPLACE PACKAGE BODY Subixclt
AS
FUNCTION BEFOREREP (P_ORDERED_BY IN VARCHAR2)RETURN BOOLEAN IS
BEGIN
--FND_FILE.PUT_LINE(FND_FILE.LOG,'L_ORDERED_by'||L_ORDERED_BY);
DECLARE
L_ORDERED_BY VARCHAR2(50);
--P_RAISEDBY VARCHAR2(50);
--P_STATUS VARCHAR2(50);
--P_CLAIMANT VARCHAR2(100);
--P_EXPENSE_DATE_FROM DATE;
--P_EXPENSE_DATE_TO DATE;
BEGIN
IF (P_ORDERED_BY='Expense Report Number') THEN
     L_ORDERED_BY :='order by 1 asc;';
ELSIF (P_ORDERED_BY='Person Claiming') THEN
     L_ORDERED_BY :='order by 2 asc;';
ELSIF (P_ORDERED_BY='Submit Date') THEN
L_ORDERED_BY :='order by 4 asc;';
RETURN TRUE;
END IF;
-- EXCEPTION WHEN OTHERS THEN RETURN FALSE;
--RETURN(L_ORDERED_BY);
END;
END;
END;error log reads:
XDO Data Engine Version No: 5.6.3
Resp: 20707
Org ID : 102
Request ID: 2484872
All Parameters: p_raisedby=SUSAN HOLLIDAY:p_status=:p_claimant=:p_expense_date_from=:p_expense_date_to=:P_ORDERED_BY=Person Claiming
Data Template Code: SUBIXCLT
Data Template Application Short Name: PO
Debug Flag: N
{p_claimant=, p_expense_date_to=, p_status=, p_raisedby=SUSAN HOLLIDAY, p_expense_date_from=, P_ORDERED_BY=Person Claiming}
Calling XDO Data Engine...
[061110_114425280][][STATEMENT] Start process Data
[061110_114425282][][STATEMENT] Process Data ...
[061110_114425284][][STATEMENT] Executing data triggers...
[061110_114425284][][STATEMENT] BEGIN
SUBIXCLT.p_claimant := :p_claimant ;
SUBIXCLT.p_expense_date_from := :p_expense_date_from ;
SUBIXCLT.p_expense_date_to := :p_expense_date_to ;
SUBIXCLT.p_raisedby := :p_raisedby ;
SUBIXCLT.p_status := :p_status ;
SUBIXCLT.p_ordered_by := :p_ordered_by ;
:XDO_OUT_PARAMETER := 1;
END;
[061110_114425287][][STATEMENT] 1: :
[061110_114425287][][STATEMENT] 2:null :
[061110_114425287][][STATEMENT] 3:null :
[061110_114425288][][STATEMENT] 4:SUSAN HOLLIDAY :
[061110_114425288][][STATEMENT] 5: :
[061110_114425288][][STATEMENT] 6:null :
[061110_114425291][][STATEMENT] Executing data triggers...
[061110_114425292][][STATEMENT] Declare
l_flag Boolean;
BEGIN
l_flag := SUBIXCLT.beforerep(:p_ordered_by) ;
if (l_flag) then
:XDO_OUT_PARAMETER := 1;
end if;
end;
[061110_114425293][][STATEMENT] 1:null :
[061110_114425302][][EXCEPTION] SQLException encounter while executing data trigger....
java.sql.SQLException: ORA-06503: PL/SQL: Function returned without value
ORA-06512: at "APPS.SUBIXCLT", line 27
ORA-06512: at line 4Many thanks for staying with this..
S

PLS-00382: expression is of wrong type

Hi,
oracle 9.2
I have to write one simple procedure to retrieve some column records from the table.
In the Begin... end block...I have written select statement
Now, if i include all the columns in the select query then procedure gets compile without any error...but when I remove any one column or select specific columns in the select query of that procedure then I get below error..
PLS-00382: expression is of wrong type
can anybody explain ?
Regards

Hi,
below has been defined in the declaration part and using the below defined cur3 for the OUT parameter.
     TYPE Rec3 IS RECORD
     col1          tab.col1%TYPE,
     col2          tab.col2%TYPE,
     col3          tab.col3%TYPE,
     col4          tab.col4%TYPE,
TYPE Cur3 IS REF CURSOR RETURN Rec3 ;
is it due to record type has been defined ?
Regards

Receiving an export file error: wrong type

I have created a movie several times in FCP and then exported the movie to QT without any problems. Now all of a sudden, I can't get the movie to export correctly. After the 2 hour export, I'll check on FCP to find that the program has shut down without an "Unexpected Shut Down" message. I check for the exported movie which I find in the saved folder. I click to open and verify the completed job, but find that I get an error instead : "Error: Wrong Type".
The last successful movie I created was September 14th, prior to the QT 7.5.5 upgrade. I thought it was the upgrade, as I found out that FCP does not do well with the new QT version, so I reverted to QT 7.5, but I am still experiencing the same problem with FCP quitting and the movie not being able to read.
What is going on? Can anyone help?

Francois:
This is a crazy solution, but this happened to me last week and this solution enabled me to open my files again -- they were all greyed out and I thought I'd lost them. I took my drive in to an Apple Store Genius Bar without resolution and spend 2 hours online with ProApps (FCE/FCP) tech support, also with no resolution.
This fix is based on the fact that FCP when it is started, it automatically opens the project that was open when it was closed. First, in FCP save the current project (this can be any project -- I created a placeholder project -- to a dummy name -- I used "save me". Close FCP and delete the dummy name ("save me") project. Now rename the project that is greyed out and provides the File Error: Wrong Type message that you would like to open to the dummy name, so that it's now called "save me". Now open FCP again. Now save the recuperated file using the original name.
Maarten
Here's what you do.

Elements 9 saved file "cannot open because it is the wrong type of file"

I have Windows XP. I just purchased Photoshop Elements 9.
I open a raw, tiff or jpg image in Elements 9, make changes to it and then save it as a tiff or jpg.
About a third of the time the icon for the saved image appears as a file and not a thumbnail of the image in my saved folder.
When I try to re-open it in Elements 9 I get the message "Cannot open because it is the wrong type of file"
I never had this problem with Elements 7.
Please help!
Mike

Every camera model has its own raw format, and Adobe can't update the camera raw plug-in until it gets the information from the manufacturer, and the process takes a while. You shouldn't have to wait more than a couple of months for this. In the meantime you can use the manufacturer's software, or try downloading the latest DNG converter to see if it can make DNG files from your camera that will work in ACR.
Incidentally, you're not talking to adobe here, just to other users like yourself.
The standlalone DNG converter download is here:
http://www.adobe.com/downloads/updates/
Just pick the DNG Converter for your platform from the pulldown menu.

.RW2 File "Cannot open because it is the wrong type of file" - P.E. 9

I just got the new Panesonic Lumix DMC-G3 and took some pictures with it today and found that Photoshop Elements couldn't open the pictures because they were the "wrong type of file". Now the file format is a Raw .RW2 and I have opened many of them before in the past and they have been just fine! I think it may be that Photoshop isn't updated yet, because I checked and I had no new updates but do any of you have any ideas as to how I could fix this?! (Besides switching to JPEG)
ADOBE IF YOU SEE THIS PLEASE UPDATE YOUR SOFTWARE SO YOUR CONSUMERS CAN OPEN THE LUMIX DMC-G3'S RAW FILES! THANK YOU!

Every camera model has its own raw format, and Adobe can't update the camera raw plug-in until it gets the information from the manufacturer, and the process takes a while. You shouldn't have to wait more than a couple of months for this. In the meantime you can use the manufacturer's software, or try downloading the latest DNG converter to see if it can make DNG files from your camera that will work in ACR.
Incidentally, you're not talking to adobe here, just to other users like yourself.
The standlalone DNG converter download is here:
http://www.adobe.com/downloads/updates/
Just pick the DNG Converter for your platform from the pulldown menu.

Can't open RAW or CR2 files anymore, Get message "Wrong type of file" HELP PLEASE

As a photographer I shoot in RAW or CR2 an di have used my photoshop elements to tweak my pictures for hte last year but now my program says "Wrong type of file"...nothing has changed, so why can't I open these any more? Anyone? please help
Thanks
Rob

What camera model and what version of the raw plug-in are you using with Elements?
It is possible the pictures are corrupted and cannot be read. You can try opening them in the Canon DPP software that should have come with your camera and try exporting as a JPG from inside there and see if it also reports a bad file. Or you can post a public download link for one of your files, here, and others can try the files in their Photoshop or Lightroom and see if they work or not.

Trying to open Camera Raw results in 'wrong type of document' error

I had to do a recovery yesterday, and luckily had everything backed up. So....All seems well now, but when I loaded some photos from my camera and tried to open the CR image, I got that message. Cannot open because it is the wrong type of document. Grrrrrrrr..... I'm running windows xp and cs3.

Open Photoshop/help/about plug-in/camera raw. You should have one and only one copy listed.
It is really not in the plug-in folder for other functions. It should be in C:\Program Files\Common Files\Adobe\Plug-Ins\CS3\File Formats. It there it should be a plug-in icon that says camera raw.8bi.
What does your system say?

Wrong type of file error message PSE 7

Error message in PSE & when I try to open images I saved. Wrong type of file, cannot be opened. Tried to remove the read-only in properties but still cannot open .jpg images. Can anyone help? Photo attached.

I do not see any attachment.
-garry

FCP project - wrong type error

I have a major problem..
my disk crashed and fortunately I was able to recover all data.. BUT
when I try to open any FCP projects it would not open just reply with *File error: Wrong type*
when I try to open it from FCP it would not even hi-light the files for possible selection..
please save my a..

Search is your friend:
http://discussions.apple.com/thread.jspa?threadID=1129775&tstart=15

VerifyError: Error #1033 Cpool entry 1 is wrong type - Java Server

Hello, there!
I need some help if someone else has already face this problem.
I have a Java server that process the bytes of a SWF File stored in the server and ouptut it to the user through a Servlet. The file was decompressed and re-compressed using the java.util.zip package.
Everything works fine on Windows Server 2008 server. But now we need migrate the server to Linux. The problem is that when I test the website now, the Flash Player throws this error: VerifyError: Error #1033 Cpool entry 1 is wrong type.
Nothing has changed on client side, not even on the SWF.
The documentation is too generic/vague about this error, only saying that this means that the SWF is corrupted. But everything runs normal on Windows Server configuration, when changed to Linux, this messages appears... what could possible be the cause?
My Windows Server is:
     . Windows Server 2008 (6.0 - x86)
     . Apache 2.2.11
     . Tomcat 6.0.16.0
     . Java JDK 1.6.0_12-b04
My CentOS Server is
     . CentOS 5.4 (2.6.18-164.15.1.el5 - i386)
     . Apache 2.2.3
     . Tomcat 6.0.16.0
     . Java JDK 1.6.0_12-b04
Please, if someone could give me a lead, I would appreciate very much!
Thank you all in advance,
CaioToOn!

Thank you, Taylor!
You were right! The problem isn't about Flash.
The problem was about encoding, with the clue of Neil Coffey I could figure out the problem. It can be checked here for anyone who interest.
Thank you again,
CaioToOn!

G41M-P23 - Wrong type of memory?

Similar Messages

Maybe you are looking for