ORA-13516

Hi
SQL> select snap_interval from dba_hist_wr_control;
SNAP_INTERVAL
+40150 00:00:00.0Can anybody please explain me what is "+40150" in above snap interval ?
Can i understand from above output that snapshot interval is set to zero ?
because of above setting when i m exec dbms_workload_repository.create_snapshot i m getting below error
SQL> EXEC DBMS_WORKLOAD_REPOSITORY.CREATE_SNAPSHOT;
BEGIN DBMS_WORKLOAD_REPOSITORY.CREATE_SNAPSHOT; END;
ERROR at line 1:
ORA-13516: AWR Operation failed: INTERVAL Setting is ZERO
ORA-06512: at "SYS.DBMS_WORKLOAD_REPOSITORY", line 99
ORA-06512: at "SYS.DBMS_WORKLOAD_REPOSITORY", line 122
ORA-06512: at line 1

Handle:      user511621
Status Level:      Newbie
Registered:      May 24, 2006
Total Posts:      467
Total Questions:      114 (109 unresolved)
so many questions & so few answers.
Can anybody please explain me what is "+40150" in above snap interval ?when all else fails, Read The Fine Manual
http://download.oracle.com/docs/cd/E11882_01/server.112/e17110/statviews_4071.htm#REFRN23462

Similar Messages

ORA-13516:AWR Operation failed:Catproc not valid

HI
I got the below error while installing Oracle 11.2.0.2.0 in linux server (2.6.18-262.el5)
ORA-13516:AWR Operation failed:Catproc not valid
ORA-06512: at 'SYS.DBMS_SWRF_INTERNAL",line 206
ORA-06512: at 'SYS.DBMS_SWRF_INTERNAL",line 239
ORA-06512: at line 1
can u please help me to fix this issue.
Thanking you

skhastagir wrote:
I did what you said and get the following. Seems like nothing happened?:
C:\Users\Administrator>sqlplus / as sysdba
SQL*Plus: Release 11.2.0.1.0 Production on Fri Aug 9 14:17:23 2013
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> C:\app\Administrator\product\11.2.0\dbhome_1\RDBMS\ADMIN\catproc.sql
SP2-0024: Nothing to change.
SQL> C:\app\Administrator\product\11.2.0\dbhome_1\RDBMS\ADMIN\utlrp.sql
SP2-0024: Nothing to change.
[oracle@localhost ~]$ oerr sp2 24
00024,0, "Nothing to change.\n"
// *Cause: There was nothing in the SQL buffer when using the CHANGE
// command.
// *Action: Make sure the SQL buffer is not empty before using the
// CHANGE command.
it should be done as below
SQL> @C:\app\Administrator\product\11.2.0\dbhome_1\RDBMS\ADMIN\catproc.sql
you neglected to actually include the "AT SIGN" @ preceding the script name

Re: ORA-13516:AWR Operation failed:Catproc not valid

Did you ever get to solving your issue? I am getting the exact same thing when creating a new database under "Database Configuration Assistant". I've tried searching all over google and haven't found a single fix or even clue on where to start looking.

Duplicate thread
https://forums.oracle.com/thread/2554900

Can't find latest snapshot while generating AWR in RAC

Hello,
we take snapshot every 20 minutes. In RAC (10.2.0.4), instance 2, run query,
SELECT snap_id, begin_interval_time, end_interval_time
FROM dba_hist_snapshot
ORDER BY 1
3391 26-AUG-10 09.00.14.425 AM
26-AUG-10 09.20.05.485 AM
3392 26-AUG-10 09.20.05.485 AM
26-AUG-10 09.41.02.558 AM
try to run AWR by using latest snapshot.
@$ORACLE_HOME/rdbms/admin/awrrpt.sql
Current Instance
~~~~~~~~~~~~~~~~
DB Id DB Name Inst Num Instance
2562639660 xxxx1 2 xxxx2
Specify the Report Type
~~~~~~~~~~~~~~~~~~~~~~~
Would you like an HTML report, or a plain text report?
Enter 'html' for an HTML report, or 'text' for plain text
Defaults to 'html'
Enter value for report_type: html
Type Specified: html
Instances in this Workload Repository schema
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DB Id Inst Num DB Name Instance Host
* 2562639660 2 xxx xxx2 xxx2
2562639660 1 xxx xxxx1 xxx1
Using 2562639660 for database Id
Using 2 for instance number
Specify the number of days of snapshots to choose from
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Entering the number of days (n) will result in the most recent
(n) days of snapshots being listed. Pressing <return> without
specifying a number lists all completed snapshots.
Enter value for num_days:
Instance DB Name Snap Id Snap Started Level
xxx2 xxx1 2836 18 Aug 2010 16:17 1
3179 23 Aug 2010 10:40 1
3180 23 Aug 2010 10:57 1
3182 23 Aug 2010 11:35 1
3187 23 Aug 2010 13:15 1
Specify the Begin and End Snapshot Ids
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Enter value for begin_snap: 3182
Begin Snapshot Id specified: 3182
Enter value for end_snap: 3187 ---the latest 'valid' snapid is 3187 not 3391???
Report written to test1
---check
select snap_id, DBID, instance_number,SNAP_LEVEL, ERROR_COUNT from dba_hist_snapshot where snap_id = 3187;
SNAP_ID DBID INSTANCE_NUMBER SNAP_LEVEL ERROR_COUNT
3187 2562639660 1 1 0
3187 2562639660 2 1 0
select snap_id, DBID, instance_number,SNAP_LEVEL, ERROR_COUNT from dba_hist_snapshot where snap_id = 3391;
SNAP_ID DBID INSTANCE_NUMBER SNAP_LEVEL ERROR_COUNT
3391 2562639660 1 1 0
seems like when we set up, we didn't collect instance_number 2's snapshot, any suggestion?
Thank you

select job_name, error#, ACTUAL_START_DATE,ADDITIONAL_INFO from dba_scheduler_job_run_details where job_name= 'SNAPSHOT_COLLECTION';
JOB_NAME
ERROR# ACTUAL_START_DATE
ADDITIONAL_INFO
SNAPSHOT_COLLECTION
13516 27-AUG-10 11.00.30.935776 AM CST6CDT
ORA-13516: AWR Operation failed: ORA-13516: AWR Operation failed: INTERVAL Setting is ZERO
ORA-06512: at "SYS.DBMS_WORKLOAD_REPOSITORY", line 10
ORA-06512: at "SYS.DBMS_WORKLOAD_REPOSITORY", line 33
ORA-06512: at line 1
OK, so I reset interval back to 20 (minutes), let me see if it works...
thank you

Problem Automatic Workload Repository after upgrage to 10.1.0.4.0

Hello everybody,
We upgraded last week a database 10g from release 10.1.0.3.0 to 10.1.0.4.0.
Since this upgrade, the AWR doesn't create any snapshot anymore but the process MMON is still living.
I tried to modify the interval of creation (reduce from 1H to 30min) of the snapshot using EM. When I execute the command I receive the following error statement:
Please correct the following error:ORA-13516: SWRF Operation failed: CATPROC not valid ORA-06512: at "SYS.DBMS_WORKLOAD_REPOSITORY", line 83 ORA-06512: at line 1
Should I re-execute some script(s) from .../RDBMS/ADMIN to fix it?
Thank a lot in advance for your support to solve this issue.

Hopefully I could find a post on the Oracle Forum to fix my issue.
I did the following operations:
1) SHUTDOWN IMMEDIATE;
2) STARTUP UPGRADE;
3) SQLPLUS / AS SYSDBA
4) @<Oracle_home>/RDBMS/ADMIN/CATPATCH.SQL
5) When the script completed check that no errors occured.
6) SHUTDOWN IMMEDIATE
7) RESTART
After this the Automatic Workload Repository could execute normally the snapshots and I was able for exemple to modify the frequence of the snapshots creation.
I only don't understand why I had to execute this sql script to get in running. Should this script not be a part of execution of the upgrade 10.1.0.3.0 to 10.1.0.4.0 ?

ADDM report not being generated

I noticed that addm reports are not being generated from last 2 days. So I did the following:
SQL> exec dbms_workload_repository.create_snapshot;
BEGIN dbms_workload_repository.create_snapshot; END;
ERROR at line 1:
ORA-13516: AWR Operation failed: only a subset of SQL can be issued
ORA-06512: at "SYS.DBMS_WORKLOAD_REPOSITORY", line 10
ORA-06512: at "SYS.DBMS_WORKLOAD_REPOSITORY", line 33
ORA-06512: at line 1
I got above error. I am not sure what that means. I also ran below SQL:
SQL> select nam.ksppinm name, val.KSPPSTVL, nam.ksppdesc description
2 from x$ksppi nam, x$ksppsv val
3 where nam.indx = val.indx and
4 nam.ksppinm = '_awr_restrict_mode'
5 order by 1
6 ;
awrrestrict_mode
FALSE
AWR Restrict Mode
What could be the reason that the reports are not being generated anymore

Check Note:308003.1 - AWR Snapshots Not Generating

Oracle Upgrade 10.2.0.3 to 10.2.0.4

Hello!
I upgraded Oracle 10.2.0.3 to 10.2.04 (on Solaris 10). The script catupgrd.sql produced a very large logfile (about 24 MB). Therefore my questions:
1.) Is there any search tool for 'real' errors in such a large output logfile?
2.) I made a grep for the string 'error' in this logfile but unfortunately Oracle doesn't quit successful finished actions with 'success' but with 'No errors'. Why 'No errors' and not 'success'? (which would make searching for errors much more sufficient) Is it an advice from the legal department?
3.) I got 1 warning:
Warning: Package Body created with compilation errors.
LINE/COL ERROR
1433/7 PL/SQL: Statement ignored
1433/28 PLS-00302: component 'CONVERT_DISTANCE' must be declared
1447/9 PL/SQL: Statement ignored
1447/26 PLS-00302: component 'CONVERT_DISTANCE' must be declared
1471/7 PL/SQL: Statement ignored
1471/24 PLS-00302: component 'EXPAND_MULTI_POINT' must be declared
Is this warning a severe one or only not declared variables in source code?
Best regards,
- kjz

grep -i ^ORA- upgrade.log
gives:
2367 -- DATABASE-NOT-MOUNTED (ora-xxxx)
2369 -- NOT-A-CONTROLFILE (ora-xxxx)
2450 -- DATABASE-NOT-MOUNTED (ora-1507)
2452 -- INVALID-RECTYPE (ora-xxxx)
2454 -- INVALID-DELTA-NUMRECS (ora-00219)
2559 -- FNAME-NOT-SPECIFIED (ora-19634)
2608 -- DEVICE-NOT-ALLOCATED (ora-19569)
2610 -- DATABASE-NOT-MOUNTED (ora-1507)
2612 -- RECOVERY-CATALOG-ERROR (ora-19633)
2615 -- FNAME-NOT-SPECIFIED (ora-19634)
2680 -- DATABASE-NOT-MOUNTED (ora-1507)
2682 -- RECOVERY-CATALOG-ERROR (ora-19633)
2685 -- FNAME-NOT-SPECIFIED (ora-19634)
2717 -- DATABASE-NOT-MOUNTED (ora-1507)
2719 -- FILE-NUMBER-NOT-FOUND (ora-19632)
2806 -- DATABASE-NOT-MOUNTED (ora-1507)
2808 -- RECORD-NOT-FOUND (ora-19571)
2810 -- RECORD-NOT-VALID (ora-19588)
2813 -- CANNOT-RENAME-TO-FILE (ora-01523)
2815 -- FILE-IS-OPEN (ora-19623)
2818 -- FILE-NOT-FOUND (ora-19625)
2820 -- FILE-VALIDATION-FAILURE (ora-19563)
2832 -- NAME-TOO-LONG (ora-19704)
2941 -- DEVICE-NOT-ALLOCATED (ora-19569)
2944 -- DATABASE-NOT-MOUNTED (ora-1507)
2946 -- RECOVERY-CATALOG-ERROR (ora-19633)
2949 -- FNAME-NOT-SPECIFIED (ora-19634)
3051 -- CONVERSATION-ACTIVE (ora-19590)
3700 -- NAME-TOO-LONG (ora-19704)
3918 -- DATABASE-NOT-MOUNTED (ora-1507)
3920 -- RMAN-CONF-NAME-TOO-LONG (ora-19677)
3923 -- RMAN-CONF-VALUE-TOO-LONG (ora-19678)
3931 -- DATABASE-NOT-MOUNTED (ora-1507)
3944 -- DATABASE-NOT-MOUNTED (ora-1507)
3946 -- INVALID-CONF-RECORD (ora-19679)
3963 -- DATABASE-NOT-MOUNTED (ora-1507)
3965 -- NAME-TOO-LONG (ora-19704)
3968 -- FILE-IN-USE (ora-19584)
3986 -- DATABASE-NOT-MOUNTED (ora-1507)
4216 -- DATABASE-NOT-MOUNTED (ora-1507)
4218 -- RECOVERY-CATALOG-ERROR (ora-19633)
4273 -- DATABASE-NOT-MOUNTED (ora-1507)
4275 -- FNAME-NOT-SPECIFIED (ora-19634)
4277 -- ARCHIVELOG-NOT-FOUND (ora-19579)
4279 -- DIFFERENT_RESETLOGS (ora-19658)
4281 -- FILE-NOT-FOUND (ora-19625)
4283 -- ARCHIVELOG-VALIDATE-ERROR (ora-19582)
4431 -- CONVERSATION-NOT-ACTIVE (ora-19580)
4433 -- CANT-GET-INSTANCE-STATE-ENQUEUE (ora-1155)
4436 -- DATABASE-NOT-MOUNTED (ora-1507)
4438 -- WRONG-CONVERSATION-TYPE (ora-19592)
4440 -- NAMING-PHASE-OVER (ora-19604)
4443 -- DUPLICATE-SPFILE (ora-19596)
4445 -- NO-SPFILE (ora-19598)
4447 -- RETRYABLE-ERROR (ora-19624)
4467 -- NAME-TOO-LONG (ora-19704)
4470 -- CONVERSATION-NOT-ACTIVE (ora-19580)
4472 -- CANT-GET-INSTANCE-STATE-ENQUEUE (ora-1155)
4475 -- WRONG-CONVERSATION-TYPE (ora-19592)
4478 -- CONVERSATION-IS-VALIDATE-ONLY (ora-19618)
4480 -- NAMING-PHASE-OVER (ora-19604)
4483 -- SPFILE-IS-ACTIVE (ora-32011)
4793 -- signal error scf_not_in_bs (ORA-19695).
4880 -- NAME-TOO-LONG (ora-19704)
4883 -- CANT-GET-INSTANCE-STATE-ENQUEUE (ora-1155)
4886 -- DATABASE-NOT-MOUNTED (ora-1507)
4888 -- CANT_IDENTIFY_FILE (ora-19505)
4890 -- NOT_A_BACKUP_PIECE (ora-19608)
5803 -- INVALID-LIMIT-NUMBER (ora-19560)
5805 -- DEVICE-NOT-ALLOCATED (ora-19569)
6372 -- NO-INPUT-FILENAME (ora-19605)
6374 -- NO-OUTPUT-FILENAME (ora-19574)
6376 -- NAME-TOO-LONG (ora-19704)
6379 -- TAG-TOO-LONG (ora-19705)
6381 -- DEVICE-PARM-TOO-LONG (ora-19702)
6383 -- CANT-GET-INSTANCE-STATE-ENQUEUE (ora-1155)
6386 -- DATABASE-NOT-MOUNTED (ora-1507)
6388 -- FILE-IN-USE (ora-19584)
6391 -- DEVICE-NOT-ALLOCATED (ora-19569)
6393 -- CANT-IDENTIFY-FILE (ora-19505)
6395 -- END-OF-VOLUME (ora-19630)
6397 -- CORRUPT_BLOCK (ora-19599)
6400 -- NOT-A-BACKUP-PIECE (ora-19608)
6402 -- CORRUPT-DIRECTORY (ora-19610)
36 -- Ora-20001 error is raised to alert the user of this.
170 -- b.) resulted in ORA-6571 : ignore it
153 -- exceed 4000, otherwise it throws ORA-19011,
20 -- An ORA-30677 indicates that the requested session is already
41 -- Likely errors to encounter here are ORA-00022, ORA-01031, ORA-30677,
42 -- ORA-30681, ORA-30682, and ORA-30683.
48 -- can only connect itself. ORA-00022 will be raised on attempts
55 -- ORA-01031 will be raised otherwise.
60 -- user; in such a case an ORA-01031 will be raised.
83 -- if an attempt without this option raised ORA-30677, then if the user
96 -- An ORA-00022 exception may be raised here.
102 -- can only connect or disconnect itself. ORA-00022 will be raised on
147 -- by this call. ORA-30689 may also be raised. Additionally, this call
186 -- bad_request (ORA-16508)
216 -- bad_request (ORA-16508)
230 -- bad_request (ORA-16508)
243 -- bad_request (ORA-16508)
259 -- bad_request (ORA-16508)
274 -- bad_request (ORA-16508)
283 -- bad_request (ORA-16508)
292 -- bad_request (ORA-16508)
sys@datas> --- if you see ORA-02292 (integrity constraint violated) and
sys@datas> --- ORA-00001 (unique constraint violated)
164 -- ORA-23304 (malformedcall) if there is an defer_rpc_arg
216 -- ORA-23304 (malformedcall) if the previous transaction
219 -- ORA-23319 Parameter value is not appropriate
220 -- ORA-23352 Raised by dbms_defer.call if the node
272 -- ORA-23304 (malformedcall) if the previous call not
275 -- ORA-23319 Parameter value is not appropriate
276 -- ORA-23352 If the destination list (specified by nodes or by a previous
131 -- ORA-23352
220 -- ORA-23605 is raised.
285 -- ORA-13516 SWRF not available
286 -- ORA-13618 invalid value for parameter instance
287 -- ORA-30014 system is running in non-AUM mode.
288 -- ORA-30029 no active undo tablespace.
102 dbms_output.put_line('retrying because of ORA-01545');
DOC>## ORA-29554: unhandled Java out of memory condition
178 -- If the java schema object does not exist an ORA-29532 (Uncaught Java
ORA-29558: JAccelerator (NCOMP) not installed. Refer to Install Guide for
ORA-06512: at "SYS.DBMS_JAVA", line 236
85 -- we must do this as a bug workaround; otherwise we get ora-600 [kgmexchi11]
57 -- we must do this as a bug workaround; otherwise we get ora-600 [kgmexchi11]
136 ORA-20000 - application error ( with an textile error stack)
159 ORA-20000 - application error ( with an textile error stack)
189 ORA-20000 - application error (with a textile error stack)
223 ORA-20000 - application error (with a textile error stack)
92 -- ORA-31001: Invalid resource handle or path name
213 -- ORA-31001: Invalid resource handle or path name
228 -- ORA-31001: Invalid resource handle or path name
241 -- ORA-31001: Invalid resource handle or path name
92 -- ORA-31001: Invalid resource handle or path name
213 -- ORA-31001: Invalid resource handle or path name
228 -- ORA-31001: Invalid resource handle or path name
241 -- ORA-31001: Invalid resource handle or path name
92 -- ORA-31001: Invalid resource handle or path name
213 -- ORA-31001: Invalid resource handle or path name
228 -- ORA-31001: Invalid resource handle or path name
241 -- ORA-31001: Invalid resource handle or path name
92 -- ORA-31001: Invalid resource handle or path name
213 -- ORA-31001: Invalid resource handle or path name
228 -- ORA-31001: Invalid resource handle or path name
241 -- ORA-31001: Invalid resource handle or path name
ORA-29831: operator binding not found
ORA-06553: PLS-306: wrong number or types of arguments in call to
ORA-06553: PLS-306: wrong number or types of arguments in call to
ORA-29831: operator binding not found
ORA-06553: PLS-306: wrong number or types of arguments in call to
ORA-29831: operator binding not found
ORA-06553: PLS-306: wrong number or types of arguments in call to
ORA-06553: PLS-306: wrong number or types of arguments in call to
ORA-29831: operator binding not found
ORA-06553: PLS-306: wrong number or types of arguments in call to
ORA-29831: operator binding not found
ORA-06553: PLS-306: wrong number or types of arguments in call to
ORA-06553: PLS-306: wrong number or types of arguments in call to
ORA-29831: operator binding not found
ORA-06553: PLS-306: wrong number or types of arguments in call to
ORA-06553: PLS-306: wrong number or types of arguments in call to
ORA-29831: operator binding not found
ORA-06553: PLS-306: wrong number or types of arguments in call to 'SDO_INSIDE'
ORA-29831: operator binding not found
ORA-06553: PLS-306: wrong number or types of arguments in call to 'SDO_INSIDE'
ORA-06553: PLS-306: wrong number or types of arguments in call to 'SDO_INSIDE'
ORA-29831: operator binding not found
ORA-06553: PLS-306: wrong number or types of arguments in call to 'SDO_INSIDE'
ORA-06553: PLS-306: wrong number or types of arguments in call to 'SDO_INSIDE'
ORA-29831: operator binding not found
ORA-06553: PLS-306: wrong number or types of arguments in call to 'SDO_TOUCH'
ORA-29831: operator binding not found
ORA-06553: PLS-306: wrong number or types of arguments in call to 'SDO_TOUCH'
ORA-06553: PLS-306: wrong number or types of arguments in call to 'SDO_TOUCH'
ORA-29831: operator binding not found
ORA-06553: PLS-306: wrong number or types of arguments in call to 'SDO_TOUCH'
ORA-06553: PLS-306: wrong number or types of arguments in call to 'SDO_TOUCH'
ORA-29831: operator binding not found
ORA-06553: PLS-306: wrong number or types of arguments in call to 'SDO_EQUAL'
ORA-29831: operator binding not found
ORA-06553: PLS-306: wrong number or types of arguments in call to 'SDO_EQUAL'
ORA-06553: PLS-306: wrong number or types of arguments in call to 'SDO_EQUAL'
ORA-29831: operator binding not found
ORA-06553: PLS-306: wrong number or types of arguments in call to 'SDO_EQUAL'
ORA-06553: PLS-306: wrong number or types of arguments in call to 'SDO_EQUAL'
ORA-29831: operator binding not found
ORA-06553: PLS-306: wrong number or types of arguments in call to 'SDO_COVERS'
ORA-29831: operator binding not found
ORA-06553: PLS-306: wrong number or types of arguments in call to 'SDO_COVERS'
ORA-06553: PLS-306: wrong number or types of arguments in call to 'SDO_COVERS'
ORA-29831: operator binding not found
ORA-06553: PLS-306: wrong number or types of arguments in call to 'SDO_COVERS'
ORA-06553: PLS-306: wrong number or types of arguments in call to 'SDO_COVERS'
ORA-29831: operator binding not found
ORA-06553: PLS-306: wrong number or types of arguments in call to
ORA-29831: operator binding not found
ORA-06553: PLS-306: wrong number or types of arguments in call to
ORA-06553: PLS-306: wrong number or types of arguments in call to
ORA-29831: operator binding not found
ORA-06553: PLS-306: wrong number or types of arguments in call to
ORA-06553: PLS-306: wrong number or types of arguments in call to
ORA-29831: operator binding not found
ORA-06553: PLS-306: wrong number or types of arguments in call to
ORA-29831: operator binding not found
ORA-06553: PLS-306: wrong number or types of arguments in call to
ORA-06553: PLS-306: wrong number or types of arguments in call to
ORA-29831: operator binding not found
ORA-06553: PLS-306: wrong number or types of arguments in call to
ORA-06553: PLS-306: wrong number or types of arguments in call to
ORA-29831: operator binding not found
ORA-06553: PLS-306: wrong number or types of arguments in call to 'SDO_ON'
ORA-29831: operator binding not found
ORA-06553: PLS-306: wrong number or types of arguments in call to 'SDO_ON'
ORA-06553: PLS-306: wrong number or types of arguments in call to 'SDO_ON'
ORA-29831: operator binding not found
ORA-06553: PLS-306: wrong number or types of arguments in call to 'SDO_ON'
ORA-06553: PLS-306: wrong number or types of arguments in call to 'SDO_ON'
ORA-29831: operator binding not found
ORA-06553: PLS-306: wrong number or types of arguments in call to
ORA-29831: operator binding not found
ORA-06553: PLS-306: wrong number or types of arguments in call to
ORA-06553: PLS-306: wrong number or types of arguments in call to
ORA-29831: operator binding not found
ORA-06553: PLS-306: wrong number or types of arguments in call to
ORA-06553: PLS-306: wrong number or types of arguments in call to
ORA-29831: operator binding not found
ORA-06553: PLS-306: wrong number or types of arguments in call to
ORA-29831: operator binding not found
ORA-06553: PLS-306: wrong number or types of arguments in call to
ORA-06553: PLS-306: wrong number or types of arguments in call to
ORA-29831: operator binding not found
ORA-06553: PLS-306: wrong number or types of arguments in call to
ORA-06553: PLS-306: wrong number or types of arguments in call to
ORA-29831: operator binding not found
ORA-06553: PLS-306: wrong number or types of arguments in call to 'SDO_FILTER'
ORA-29831: operator binding not found
ORA-06553: PLS-306: wrong number or types of arguments in call to 'SDO_FILTER'
ORA-29831: operator binding not found
ORA-06553: PLS-306: wrong number or types of arguments in call to 'SDO_FILTER'
2 'Code for the error encountered : ORA-XXXXX';
2 'Code for the error encountered : ORA-XXXXX';
grep -i ^SP2- upgrade.log has no output.
Status of components is all valid:
Oracle Database 10.2 Upgrade Status Utility 11-19-2008 12:35:27
Component Status Version HH:MM:SS
Oracle Database Server VALID 10.2.0.4.0 00:24:03
JServer JAVA Virtual Machine VALID 10.2.0.4.0 00:05:11
Oracle XDK VALID 10.2.0.4.0 00:00:58
Oracle Database Java Packages VALID 10.2.0.4.0 00:01:05
Oracle Text VALID 10.2.0.4.0 00:00:34
Oracle XML Database VALID 10.2.0.4.0 00:05:04
Oracle Workspace Manager VALID 10.2.0.4.3 00:01:10
Oracle Data Mining VALID 10.2.0.4.0 00:00:36
Oracle interMedia VALID 10.2.0.4.0 00:09:39
Oracle Expression Filter VALID 10.2.0.4.0 00:00:23
Oracle Rule Manager VALID 10.2.0.4.0 00:00:17
PL/SQL procedure successfully completed.
Regards,
- kjz

Solotion upgrade to 10.1.0.3, it show internal 500 error im em web console

Note:
solotion upgrade from 10.1.0.2 to 10.1.0.3, it show internal 500 error im em web console
If you do not run the catpatch.sql script as described in this section and you start up a database for normal operation, then "ORA-13516: SWRF Operation failed: CATPROC not valid" errors will occur.
For RAC installations, start node applications on each node of the cluster as follows:
$ srvctl start nodeapps -n nodename
For single-instance installations, start the listener as follows:
$ lsnrctl start
Note:
If you are using the Oracle OLAP option, make sure that the listener is running.
If you are using ASM, start the ASM instance.
Use SQL*Plus to login to the database as the SYS user with SYSDBA privileges:
$ sqlplus "/ AS SYSDBA"
Start the database:
SQL> STARTUP
Set the value of the SHARED_POOL_SIZE initialization parameter to at least 150 MB:
SQL> ALTER SYSTEM SET SHARED_POOL_SIZE='150M' SCOPE=spfile;
Set the value of the JAVA_POOL_SIZE initialization parameter to at least 120 MB:
SQL> ALTER SYSTEM SET JAVA_POOL_SIZE='120M' SCOPE=spfile;
Shut down the database:
SQL> SHUTDOWN
Enter the following SQL*Plus commands:
Note:
If you are applying this patch set to a cluster database, then set the CLUSTER_DATABASE initialization parameter to FALSE before starting it in upgrade mode. After you have run the catpatch.sql script, reset this initialization parameter to TRUE.
SQL> STARTUP UPGRADE
SQL> SPOOL patch.log
SQL> @?/rdbms/admin/catpatch.sql
SQL> SPOOL OFF
Review the patch.log file for errors and inspect the list of components that is displayed at the end of catpatch.sql script.
This list provides the version and status of each SERVER component in the database.
If necessary, rerun the catpatch.sql script after correcting any problems.
Restart the database:
SQL> SHUTDOWN
SQL> STARTUP
Run the utlrp.sql script to recompile all invalid PL/SQL packages now instead of when the packages are accessed for the first time. This step is optional but recommended.
SQL> @?/rdbms/admin/utlrp.sql
Note:
When the 10.1.0.3 patch set is applied to an Oracle Database 10g Standard Edition database, there may be 42 invalid objects after the utlrp.sql script runs. These objects belong to the unsupported components and do not affect the database operation.
If you are using the Oracle Recovery Manager catalog, enter the following command:
$ rman catalog username/password@alias
RMAN> UPGRADE CATALOG;

Note:
solotion upgrade from 10.1.0.2 to 10.1.0.3, it show internal 500 error im em web console
If you do not run the catpatch.sql script as described in this section and you start up a database for normal operation, then "ORA-13516: SWRF Operation failed: CATPROC not valid" errors will occur.
For RAC installations, start node applications on each node of the cluster as follows:
$ srvctl start nodeapps -n nodename
For single-instance installations, start the listener as follows:
$ lsnrctl start
Note:
If you are using the Oracle OLAP option, make sure that the listener is running.
If you are using ASM, start the ASM instance.
Use SQL*Plus to login to the database as the SYS user with SYSDBA privileges:
$ sqlplus "/ AS SYSDBA"
Start the database:
SQL> STARTUP
Set the value of the SHARED_POOL_SIZE initialization parameter to at least 150 MB:
SQL> ALTER SYSTEM SET SHARED_POOL_SIZE='150M' SCOPE=spfile;
Set the value of the JAVA_POOL_SIZE initialization parameter to at least 120 MB:
SQL> ALTER SYSTEM SET JAVA_POOL_SIZE='120M' SCOPE=spfile;
Shut down the database:
SQL> SHUTDOWN
Enter the following SQL*Plus commands:
Note:
If you are applying this patch set to a cluster database, then set the CLUSTER_DATABASE initialization parameter to FALSE before starting it in upgrade mode. After you have run the catpatch.sql script, reset this initialization parameter to TRUE.
SQL> STARTUP UPGRADE
SQL> SPOOL patch.log
SQL> @?/rdbms/admin/catpatch.sql
SQL> SPOOL OFF
Review the patch.log file for errors and inspect the list of components that is displayed at the end of catpatch.sql script.
This list provides the version and status of each SERVER component in the database.
If necessary, rerun the catpatch.sql script after correcting any problems.
Restart the database:
SQL> SHUTDOWN
SQL> STARTUP
Run the utlrp.sql script to recompile all invalid PL/SQL packages now instead of when the packages are accessed for the first time. This step is optional but recommended.
SQL> @?/rdbms/admin/utlrp.sql
Note:
When the 10.1.0.3 patch set is applied to an Oracle Database 10g Standard Edition database, there may be 42 invalid objects after the utlrp.sql script runs. These objects belong to the unsupported components and do not affect the database operation.
If you are using the Oracle Recovery Manager catalog, enter the following command:
$ rman catalog username/password@alias
RMAN> UPGRADE CATALOG;

Manual snapshot failure

When I try to run a manual snapshot with EM I get the following error.
SQL Error
ORA-13516: AWR Operation failed: INTERVAL Setting is ZERO ORA-06512: at "SYS.DBMS_WORKLOAD_REPOSITORY", line 10 ORA-06512: at "SYS.DBMS_WORKLOAD_REPOSITORY", line 33 ORA-06512: at line 1
Being new I do not understand enough to just go in and fix this.
Could someone please help with an explanation of why this error generates..
Thanks in advance,
d.

You cannot run a Manual Snapshot if the System Snapshot Interval is set to 0
Ensure you are loggoed in to the Database with user with SYSDBA privilege. Edit the Snapshot settings, view and correct the entry for System Snapshot Interval.

PL/SQL report errors: ORA-01422

Hi all,
(before i you read i would like to say i have searched the net for this error code but nothing shows up like this problem..)
I am getting an error problem when i select certain Schemas from a list on an apex app. page, it only works for some schemas not all..
When i select one schema, it is supposed to display one row.. when i select [ALL] it is supposed to show them all.
It does work if i select '[ALL]' from the select list (p3_schema_name), just not for every single individual one.
the error code:
ORA-01422: exact fetch returns more than requested number of rows
declare
vSchema varchar2(20);
vStmt varchar2(1000);
vVersion number(5);
vDBName varchar2(20);
vHostName varchar2(80);
vStmt2 varchar2(1000);
vVersion2 number(5);
vDBName2 varchar2(20);
vServer2 varchar2(80);
vSchema2 varchar2(80);
CURSOR c_schemas IS
    select owner from dba_tables@P3_DB_NAME.db_link where table_name = 'DDL_LOG' and num_rows > 0 order by owner;
begin
IF :P3_SCHEMA_NAME != '[ALL]' AND :P3_DB_NAME IS NOT NULL AND :P3_SERVER_NAME IS NOT NULL THEN
    vServer2 := :P3_SERVER_NAME;
    vSchema2 := :P3_SCHEMA_NAME;
      vStmt2 := 'select distinct DDH_DB_NM, max(DDH_SCHEMA_NR)keep(dense_rank last order by ddh_runstart_td) AS "PATCH" from &P3_SCHEMA_NAME..ddl_log@&P3_DB_NAME.db_link GROUP BY DDH_DB_NM';
      Execute Immediate vStmt2 into vDBName2, vVersion2;
        htp.p('<br>');
        htp.p('<table border="1">');
        htp.p('<tr>');
        htp.p('<th bgcolor="#FFCC99">SERVER NAME</th>');
        htp.p('<th bgcolor="#FFCC99">DB NAME</th>');
        htp.p('<th bgcolor="#FFCC99">SCHEMA NAME</th>');
        htp.p('<th bgcolor="#FFCC99">PATCH</th>');
        htp.p('</tr>');
        htp.p('<tr>');
        htp.p('<td>');
        htp.p(vServer2);
        htp.p('</td>');
        htp.p('<td>');
        htp.p(vDBName2);
        htp.p('</td>');
        htp.p('<td>');
        htp.p(vSchema2);
        htp.p('</td>');
        htp.p('<td>');
        htp.p(vVersion2);
        htp.p('</td>');
        htp.p('<td>');
        htp.p('<BR>');
        htp.p('</td>');
        htp.p('</tr>');
        htp.p('</tr>');
        htp.p('</table>');
   ELSE IF :P3_SCHEMA_NAME = '[ALL]' AND :P3_DB_NAME IS NOT NULL AND :P3_SERVER_NAME IS NOT NULL THEN
   vHostName := :P3_SERVER_NAME;
   vDBName := :P3_DB_NAME;
     open c_schemas;
      htp.p('<br>');
      htp.p('<table border="1">');
      htp.p('<tr>');
      htp.p('<th bgcolor="#FFCC99">SERVER NAME</th>');
      htp.p('<th bgcolor="#FFCC99">DB NAME</th>');
      htp.p('<th bgcolor="#FFCC99">SCHEMA NAME</th>');
      htp.p('<th bgcolor="#FFCC99">PATCH</th>');
      htp.p('</tr>');
    LOOP
      FETCH c_schemas INTO vSchema;
      EXIT WHEN c_schemas%NOTFOUND;
      vStmt := 'select max(DDH_SCHEMA_NR)keep(dense_rank last order by ddh_runstart_td) AS "PATCH" from '||vSchema||'.ddl_log@&P3_DB_NAME.db_link where DDH_SCHEMA_NR = (select max(DDH_SCHEMA_NR) from '||vSchema||'.ddl_log@&P3_DB_NAME.db_link) and rownum < 2' ;
      Execute Immediate vStmt into vVersion ;
      htp.p('<tr>');
      htp.p('<td>');
      htp.p(vHostName);
      htp.p('</td>');
      htp.p('<td>');
      htp.p(vDBName);
      htp.p('</td>');
      htp.p('<td>');
      htp.p(vSchema);
      htp.p('</td>');
      htp.p('<td>');
      htp.p(vVersion);
      htp.p('</td>');
      htp.p('<td>');
      htp.p('<BR>');
      htp.p('</td>');
      htp.p('</tr>');
    END LOOP;
      htp.p('</tr>');
      htp.p('</table>');
CLOSE c_schemas;
END IF;
END IF;
END;I have checked the DDH_SCHEMA_NR for repeating entries of the highest number.. some of the ones that dont work do have repeating entries some don't.
Sorry if this is confusing, i have tried to explain it as best as i can.
Thanks in advance for any help.
Ashleigh

Hello Ashleigh,
Based on your code, I'd start by running this piece of SQL via command-line (thru SQL Workshop, SQL*Plus, Toad, etc.), replacing &P3_SCHEMA_NAME. and &P3_DB_NAME. with values that are currently causing the routine to fail and see if it returns more than one row. I don't know your data, but DISTINCT and GROUP BY are typically used to return multiple (though grouped/summarized) rows. It appears to be the only statement that would cause the error your seeing (more than one row being returned into single variables).
select distinct DDH_DB_NM, max(DDH_SCHEMA_NR)keep(dense_rank last order by ddh_runstart_td) AS "PATCH" from &P3_SCHEMA_NAME..ddl_log@&P3_DB_NAME.db_link GROUP BY DDH_DB_NM;I'm actually surprised that the code runs at all. I didn't think 'execute immediate' would know what to do with substitutions indicated as "&something." (I've typically seen that when substituting in dynamic HTML/Javascript code but maybe I'm learning something new). But since you already have vServer2 and vSchema2, I'd be more apt to code it as:
vStmt2 := 'select distinct DDH_DB_NM, max(DDH_SCHEMA_NR)keep(dense_rank last order by ddh_runstart_td) AS "PATCH" from ' ||
vSchema2 || '.ddl_log@' || vServer2 || '.db_link GROUP BY DDH_DB_NM';Hope this helps,
John

Ora-00604 error and ora 01000 error while report generation.

hi all,
I am trying to generate the multiple reports of same template through a program.
While this job is running, i get the following error at the BIP console and the reports don't get generated.
[101711_044115578][][EXCEPTION] java.sql.SQLException: ORA-00604: error occurred
at recursive SQL level 1
ORA-01000: maximum open cursors exceeded
ORA-00604: error occurred at recursive SQL level 1
ORA-01000: maximum open cursors exceeded
ORA-01000: maximum open cursors exceeded
Kindly help.
Thanks.

Lots of resources with a simple search to see what this is about, for example:
http://www.orafaq.com/wiki/ORA-01000
ORA-01000:     maximum open cursors exceeded
Cause:     A host language program attempted to open too many cursors. The initialization parameter OPEN_CURSORS determines the maximum number of cursors per user.
Action:     Modify the program to use fewer cursors. If this error occurs often, shut down Oracle, increase the value of OPEN_CURSORS, and then restart Oracle.
open_cursors parameter
http://download.oracle.com/docs/cd/E11882_01/server.112/e25513/initparams160.htm#REFRN10137
Oracle support note:
OERR: ORA-1000 maximum open cursors exceeded (Doc ID 18591.1)

EA2: ORA-01427 clicking on a view in the navigator

SQLDev: 1.5.0.52.03
Java: 1.6.0_04
Oracle: 9.2.0.7.0
I'm getting the following error when I click on a view in the navigator pane:
An error was encountered performing the requested operation:
ORA-01427: single-row subquery returns more than one row 01427. 00000 - "single-row subquery returns more than one row"I'm not seeing any errors in the shell window.
After clicking on <OK> in the error dialog, the normal tabs (Columns, Data, Grants, Dependencies, Details, SQL) are displayed, but there is no content in the Columns tab.
All the other tabs seem to function normally.
Here is the DDL from the SQL tab
CREATE OR REPLACE VIEW "SUBSCRIPTIONS"
    "ORDER_ID", "SUNBURST_ORDER_ID", "SIEBEL_ORDER_ID", "ACCOUNT_ID",
    "COMP_ID", "SUBACCOUNT_ID", "START_DATE", "END_DATE", "PULL_DATE",
    "SUBSCRIPTION_TYPE", "PRICE_CLASS", "DESCRIPTION", "SEAT_COUNT",
    "ORDER_DURATION", "CALLBACK_INTERVAL", "UPDATE_DATE", "UPDATE_USERNAME",
    "AFFILIATE"
AS
    SELECT order_id,
        sunburst_order_id,
        siebel_order_id,
        account_id,
        comp_id,
        subaccount_id,
        start_date,
        end_date,
        pull_date,
        product_id,
        price_class,
        product_name,
        add_users,
        order_duration,
        callback_interval,
        last_mdfy_date,
        last_mdfy_emp,
        affiliate
    FROM csbcrossworlds.subscriptions;We have 15 views in this schema, 3 of them fail this way but the other 12 display the columns just fine. So far I am unable to detect any commonality.
Any ideas?

Ok, I think I found the problem. The view in question (SUBSCRIPTIONS) is owned by 'PHILC' and it references a table named 'SUBSCRIPTIONS' owned by 'CSBCROSSWORLDS'. There are two other development schemas that also own tables named 'SUBSCRIPTIONS'.
I believe the 'Columns' tab is executing the query below. The subquery in this SQL tries to identify the primary key columns for the 'SUBSCRIPTIONS' view in my schema (PHILC):
SELECT
    c.column_name,
    DECODE(
        data_type,
            'CHAR',      data_type||'('||c.data_length||')',
            'VARCHAR',   data_type||'('||c.data_length||')',
            'VARCHAR2', data_type||'('||c.data_length||')',
            'NCHAR'   , data_type||'('||c.data_length||')',
            'NUMBER' , DECODE(c.data_precision,null,'NUMBER', data_type||'('||c.data_precision||','||c.data_SCALE||')'),
            'NVARCHAR', data_type||'('||c.data_length||')',
            'NVARCHAR2', data_type||'('||c.data_length||')',
            data_type) data_type,
    DECODE(nullable, 'Y', 'Yes', 'No') nullable,
    c.DATA_DEFAULT,
    column_id,
    com.comments,
    (SELECT 1 FROM all_constraints, all_cons_columns
      WHERE all_constraints.constraint_type = 'P' AND
            all_constraints.constraint_name = all_cons_columns.constraint_name AND
            all_constraints.owner = all_cons_columns.owner AND
            all_cons_columns.table_name = c.table_name AND
            c.column_name = all_cons_columns.column_name) Primary_Key,
    c_update.insertable,
    c_update.updatable,
    c_update.deletable
FROM
    sys.all_tab_Columns c, sys.all_col_comments com, sys.user_updatable_columns c_update
WHERE
    c.owner = :OBJECT_OWNER AND
    c.table_name = :OBJECT_NAME AND
    c.table_name = com.table_name AND
    c.owner = com.owner AND
    c.column_name = com.column_name AND
    c_update.column_name = com.column_name AND
    c_update.table_name = com.table_name
;Extracting the subquery into this:
SELECT
    all_constraints.owner,
    all_constraints.table_name,
    all_constraints.constraint_name
FROM all_constraints, all_cons_columns
WHERE
    all_constraints.constraint_type = 'P' AND
    all_constraints.constraint_name = all_cons_columns.constraint_name AND
    all_constraints.owner = all_cons_columns.owner and
    all_cons_columns.table_name = 'SUBSCRIPTIONS' and
    'ORDER_ID' = all_cons_columns.column_name;I got this output:
   owner          table_name      constraint_name
CUTOVER          SUBSCRIPTIONS    SUBSCRIPTIONS_PK
CROSSWORLDS      SUBSCRIPTIONS    SUBSCRIPTIONS_PK
CSBCROSSWORLDS   SUBSCRIPTIONS    SUBSCRIPTIONS_PKLooking at the DDL for the view, the row we really want is for owner 'CSBCROSSWORLDS'. Unfortunately, that means having to somehow parse the SQL text to extract the owner name...
Phil

Using database-link in view to get around ORA-01031 error

I have been granted select rights on a users table. I am therefore able to select from his table. If however I try create a view against his table I run into the ORA-01031 problem. I have worked around this problem by creating a database-link to myself and then adding that to the view creation and it works. What are the downsides of using the database-link in this way?

The only down side I have been able to identify is that a extra session is created and that the CPU has a little extra work due to the LOOP BACK that takes place. I need to ensure the network is not unnessesarly used and therefore will need to ensure that 127.0.0.1 (local host) is used in the database connection discription. e.g.
create database link my_db_link connect to scott identified by tiger using '(description=(address=(protocol=tcp)(host=127.0.0.1) (Port = 1521) ) (connect_data= (sid=ora10g)))';

Getting ora:00904 invalid indentifier error while running i query

Hi,
I have a remote database and local database both are oracle 10gR2.Now i have written the below mentioned query in my local database and is working fine,but in case remote database it is throughing error ora:00904 invalid indentifier.
I had export the dump from remote db and import it on my local db and i tried the same and it is working fine on local after that also.
As i believe that this error usually come for column name not exist or column name or it's length or for any special character in column name of the table.But as i said it is working fine on local db but not in remote db though i am using the same dump for local and remote.
Though when i am querying the table i can able to fetch data for the any record but when i am using the below mentioned query for the same i am getting the error.As i am doing this to fecth the data for child parent related relationship.
Can any one suggest is there anything related to configaration or something else.
Please do let me know if you do want some more information on the query what i am doing inside of it.
Rgds,
Anit
Edited by: Anit A. on Sep 1, 2008 2:32 AM
Edited by: Anit A. on Sep 1, 2008 2:33 AM

WITH t
AS
SELECT decode(t.spnlevel
,3,t.u_quotesdtlid
,2,decode((select count(*)
from u_quotesdtl t2
where t2.u_quotesdtlid = t.u_quotesdtlid
and t2.parentspn = (t2.jobgroupid||':'||t2.jobtype)
),0,(select t1.u_quotesdtlid
from u_quotesdtl t1
where t1.spnitemcode = t.parentspn
and t1.spnlevel = '3'
and t1.jobtype = t.jobtype
and t1.jobgroupid = t.jobgroupid
and t1.QUOTEID = t.QUOTEID
),t.u_quotesdtlid
,1,decode((select count(*)
from u_quotesdtl t2
where t2.QUOTEID = t.QUOTEID
and t2.parentspn = (t2.jobgroupid||':'||t2.jobtype)
),0,t.u_quotesdtlid,decode((select count(*)
from u_quotesdtl t3
where t3.QUOTEID = t.QUOTEID
and t3.parentspn = (t3.jobgroupid||':'||t3.jobtype)
and t3.u_quotesdtlid in (select t1.u_quotesdtlid
from u_quotesdtl t1
where t1.spnitemcode = t.parentspn
and t1.spnlevel = '2'
and t1.jobtype = t.jobtype
and t1.jobgroupid = t.jobgroupid
and t1.QUOTEID = t.QUOTEID
),0,(select t4.u_quotesdtlid
from u_quotesdtl t4
,(select t1.parentspn
,t1.jobtype
,t1.jobgroupid
from u_quotesdtl t1
where t1.spnitemcode = t.parentspn
and t1.spnlevel = '2'
and t1.jobtype = t.jobtype
and t1.jobgroupid = t.jobgroupid
and t1.QUOTEID = t.QUOTEID
) t5
where t4.spnitemcode = t5.parentspn
and t4.spnlevel = '3'
and t4.jobtype = t5.jobtype
and t4.jobgroupid = t5.jobgroupid
and t4.QUOTEID = t.QUOTEID
(select t1.u_quotesdtlid
from u_quotesdtl t1
where t1.spnitemcode = t.parentspn
and t1.spnlevel = '2'
and t1.jobtype = t.jobtype
and t1.jobgroupid = t.jobgroupid
and t1.QUOTEID = t.QUOTEID
,null,t.u_quotesdtlid) as parentquoteid
,t.u_quotesdtlid as quotesdtlid
,t.spnlevel as spnlevel
FROM u_quotesdtl t
WHERE t.QUOTEID ='som key id'
ORDER BY parentquoteid,t.spnlevel desc
select * from t;

'ORA-01722: Invalid Number' error while Running a Query

Hi,
I'm trying to run a query built on a DSO. The DSO has a field 'Start Date'. This Start Date InfoObject has a reference Char as 0DATE.
This Start Field has blank values due to which I'm getting the ORA-01722 error. I came across many threads with same topic of discussion. As mentioned in one of the Threads I have written a program to update 'Start Date' with 00000000. The code wriiten is "UPDATE /BIC/AZ_MONINV00 SET /BIC/ZSTR_DTE = '00000000' where /BIC/ZSTR_DTE = ' '.
Now when I see the data in the active data table of DSO the blank value is replaced with '00000000'.
But If I right click on the DSO click on display data the 'Start Date' field is blank. And now the Query also gets executed without any error. But in the output of the query the 'Start Date' Field has "#" values.
Can anyone suggest on how can I make these "#" values appear as 00000000 in the report?

In this case, you have to write a macro to avoid # in Analyzer.
Right Click-->Display Data will show data from Active table of DSO only.
If you don't want to show any blank date values in the report, you can exclude in Filter in Query.

ORA-13516

Similar Messages

Maybe you are looking for