When queried v$dataguard_stats results no rows selected at standby db?

Hi Chaps,
I have oracle database 10g 10.2.0.4.0 on AIX version 5.3
I am curious about standby database that whether it is in sync with the primary database or not?
when I queried at standby to know dataguard stats the result was 'no rows selected'
SELECT * FROM V$DATAGUARD_STATS ;
then I tried to know the role of the database on standby like this
SYS@prod>select name,database_role from v$database;
then the result was as follows:
NAME DATABASE_ROLE
PROD PRIMARY
is this mean that it is still a primary database and not replicating the changes from primary DB?
please enlight your thoughts to confirm a standby db is doing right job or not?
Thanks
QA

Hi, here is the init parameters from standby db
SYS@sisprod>show parameter;
NAME TYPE VALUE
O7_DICTIONARY_ACCESSIBILITY boolean FALSE
active_instance_count integer
aq_tm_processes integer 0
archive_lag_target integer 0
asm_diskgroups string
asm_diskstring string
asm_power_limit integer 1
audit_file_dest string /u01/app/oracle/product/10.2/r
dbms/audit
audit_sys_operations boolean FALSE
audit_syslog_level string
audit_trail string DB
background_core_dump string partial
background_dump_dest string /u01/app/oracle/product/10.2/a
dmin/sisprod/bdump
backup_tape_io_slaves boolean FALSE
bitmap_merge_area_size integer 1048576
blank_trimming boolean FALSE
buffer_pool_keep string
buffer_pool_recycle string
circuits integer
cluster_database boolean FALSE
cluster_database_instances integer 1
cluster_interconnects string
commit_point_strength integer 1
commit_write string
compatible string 10.2.0.1.0
control_file_record_keep_time integer 21
control_files string /u01/oradata/sisprod/control01
.ctl, /u02/oradata/sisprod/con
trol02.ctl, /u05/oradata/sispr
od/control03.ctl
core_dump_dest string /u01/app/oracle/product/10.2/a
dmin/sisprod/cdump
cpu_count integer 2
create_bitmap_area_size integer 8388608
create_stored_outlines string
cursor_sharing string EXACT
cursor_space_for_time boolean FALSE
db_16k_cache_size big integer 0
db_2k_cache_size big integer 0
db_32k_cache_size big integer 0
db_4k_cache_size big integer 0
db_8k_cache_size big integer 0
db_block_buffers integer 0
db_block_checking string TRUE
db_block_checksum string TRUE
db_block_size integer 8192
db_cache_advice string ON
db_cache_size big integer 32M
db_create_file_dest string
db_create_online_log_dest_1 string
db_create_online_log_dest_2 string
db_create_online_log_dest_3 string
db_create_online_log_dest_4 string
db_create_online_log_dest_5 string
db_domain string satelliteinfo.co.uk
db_file_multiblock_read_count integer 16
db_file_name_convert string
db_files integer 200
db_flashback_retention_target integer 1440
db_keep_cache_size big integer 0
db_name string sisprod
db_recovery_file_dest string
db_recovery_file_dest_size big integer 0
db_recycle_cache_size big integer 0
db_unique_name string sisprod
db_writer_processes integer 1
dbwr_io_slaves integer 0
ddl_wait_for_locks boolean FALSE
dg_broker_config_file1 string /u01/app/oracle/product/10.2/d
bs/dr1sisprod.dat
dg_broker_config_file2 string /u01/app/oracle/product/10.2/d
bs/dr2sisprod.dat
dg_broker_start boolean TRUE
disk_asynch_io boolean TRUE
dispatchers string
distributed_lock_timeout integer 60
dml_locks integer 748
drs_start boolean FALSE
event string
fal_client string
fal_server string
fast_start_io_target integer 0
fast_start_mttr_target integer 300
fast_start_parallel_rollback string LOW
file_mapping boolean FALSE
fileio_network_adapters string
filesystemio_options string asynch
fixed_date string
gc_files_to_locks string
gcs_server_processes integer 0
global_context_pool_size string
global_names boolean FALSE
hash_area_size integer 1048576
hi_shared_memory_address integer 0
hs_autoregister boolean TRUE
ifile file
instance_groups string
instance_name string sisprod
instance_number integer 0
instance_type string RDBMS
java_max_sessionspace_size integer 0
java_pool_size big integer 160M
java_soft_sessionspace_limit integer 0
job_queue_processes integer 15
large_pool_size big integer 32M
ldap_directory_access string NONE
license_max_sessions integer 0
license_max_users integer 0
license_sessions_warning integer 0
local_listener string
lock_name_space string
lock_sga boolean FALSE
log_archive_config string
log_archive_dest string
log_archive_dest_1 string LOCATION=/u02/oradata/sisprod/
archive
log_archive_dest_10 string
log_archive_dest_2 string SERVICE=SISPROD_STDBY LGWR ASY
NC AFFIRM NET_TIMEOUT=60 VALID
FOR=(ONLINELOGFILES,PRIMARY_
ROLE) DB_UNIQUE_NAME=SISPROD_S
TDBY
log_archive_dest_3 string
log_archive_dest_4 string
log_archive_dest_5 string
log_archive_dest_6 string
log_archive_dest_7 string
log_archive_dest_8 string
log_archive_dest_9 string
log_archive_dest_state_1 string enable
log_archive_dest_state_10 string enable
log_archive_dest_state_2 string ENABLE
log_archive_dest_state_3 string enable
log_archive_dest_state_4 string enable
log_archive_dest_state_5 string enable
log_archive_dest_state_6 string enable
log_archive_dest_state_7 string enable
log_archive_dest_state_8 string enable
log_archive_dest_state_9 string enable
log_archive_duplex_dest string
log_archive_format string %t_%s_%r.dbf
log_archive_local_first boolean TRUE
log_archive_max_processes integer 2
log_archive_min_succeed_dest integer 1
log_archive_start boolean FALSE
log_archive_trace integer 0
log_buffer integer 14246912
log_checkpoint_interval integer 0
log_checkpoint_timeout integer 1800
log_checkpoints_to_alert boolean FALSE
log_file_name_convert string
logmnr_max_persistent_sessions integer 1
max_commit_propagation_delay integer 0
max_dispatchers integer
max_dump_file_size string UNLIMITED
max_enabled_roles integer 150
max_shared_servers integer
nls_calendar string
nls_comp string
nls_currency string #
nls_date_format string DD/MM/YYYY
nls_date_language string
nls_dual_currency string
nls_iso_currency string UNITED KINGDOM
nls_language string ENGLISH
nls_length_semantics string BYTE
nls_nchar_conv_excp string FALSE
nls_numeric_characters string
nls_sort string
nls_territory string UNITED KINGDOM
nls_time_format string
nls_time_tz_format string
nls_timestamp_format string
nls_timestamp_tz_format string
object_cache_max_size_percent integer 10
object_cache_optimal_size integer 102400
olap_page_pool_size big integer 0
open_cursors integer 1500
open_links integer 4
open_links_per_instance integer 4
optimizer_dynamic_sampling integer 2
optimizer_features_enable string 10.2.0.4
optimizer_index_caching integer 0
optimizer_index_cost_adj integer 100
optimizer_mode string ALL_ROWS
optimizer_secure_view_merging boolean TRUE
os_authent_prefix string ops$
os_roles boolean FALSE
parallel_adaptive_multi_user boolean TRUE
parallel_automatic_tuning boolean FALSE
parallel_execution_message_size integer 2152
parallel_instance_group string
parallel_max_servers integer 20
parallel_min_percent integer 0
parallel_min_servers integer 0
parallel_server boolean FALSE
parallel_server_instances integer 1
parallel_threads_per_cpu integer 2
pga_aggregate_target big integer 221459251
plsql_ccflags string
plsql_code_type string INTERPRETED
plsql_compiler_flags string INTERPRETED, NON_DEBUG
plsql_debug boolean FALSE
plsql_native_library_dir string
plsql_native_library_subdir_count integer 0
plsql_optimize_level integer 2
plsql_v2_compatibility boolean FALSE
plsql_warnings string DISABLE:ALL
pre_11g_enable_capture boolean FALSE
pre_page_sga boolean FALSE
processes integer 150
query_rewrite_enabled string FALSE
query_rewrite_integrity string enforced
rdbms_server_dn string
read_only_open_delayed boolean FALSE
recovery_parallelism integer 0
recyclebin string on
remote_archive_enable string true
remote_dependencies_mode string TIMESTAMP
remote_listener string
remote_login_passwordfile string EXCLUSIVE
remote_os_authent boolean FALSE
remote_os_roles boolean FALSE
replication_dependency_tracking boolean TRUE
resource_limit boolean FALSE
resource_manager_plan string
resumable_timeout integer 0
rollback_segments string
serial_reuse string disable
service_names string sisprod.satelliteinfo.co.uk
session_cached_cursors integer 20
session_max_open_files integer 20
sessions integer 170
sga_max_size big integer 1056M
sga_target big integer 1056M
shadow_core_dump string partial
shared_memory_address integer 0
shared_pool_reserved_size big integer 10905190
shared_pool_size big integer 208M
shared_server_sessions integer
shared_servers integer 0
skip_unusable_indexes boolean TRUE
smtp_out_server string
sort_area_retained_size integer 0
sort_area_size integer 524288
spfile string /u01/app/oracle/product/10.2/d
bs/spfilesisprod.ora
sql92_security boolean FALSE
sql_trace boolean FALSE
sql_version string NATIVE
sqltune_category string DEFAULT
standby_archive_dest string ?/dbs/arch
standby_file_management string AUTO
star_transformation_enabled string FALSE
statistics_level string TYPICAL
streams_pool_size big integer 48M
tape_asynch_io boolean TRUE
thread integer 0
timed_os_statistics integer 0
timed_statistics boolean TRUE
trace_enabled boolean TRUE
tracefile_identifier string
transactions integer 187
transactions_per_rollback_segment integer 5
undo_management string AUTO
undo_retention integer 10800
undo_tablespace string UNDOTBS1
use_indirect_data_buffers boolean FALSE
use_sigio boolean TRUE
user_dump_dest string /u01/app/oracle/product/10.2/a
dmin/sisprod/udump
utl_file_dir string /u01/app/oracle/product/10.2/a
dmin/sisprod/udump
workarea_size_policy string AUTO
Thanks
QA

Similar Messages

Automatically exit window when a line in result view is selected

Dear Experts,
I am stuck with a small problem. I have create a custom component with search view and result view. Now in Component BT111h_oppt, when i have an item list assignment block. When i search for a product using F4, i have a standard search coming up. When i do the search and select a line in the result view, the system automatically shuts the window and comes back to the oppt overview page. Now i have replaced the standard search with my custom search, upon pressing F4, my custom search windows opens up and search words as normal. however, when i select any item, my window doesnt close and i have to close the window manually to come back to the oppt overview page. So, i need help to automatically close the search window when my table line is selected.
Any pointers would certainly help.
Thank you all,
Regards,
Pradeep

Hi Pradeep,
Try this..in the do_output_prepare ..write the code to check if the line is selected ..
lr_col ?= me->typed_context->contextname->collection_wrapper->get_marked( ).
check lr_col is bound.
If marked (selected) call a outbound plug of that view (eg : OP_CLOSE( ).). In that outbound plug call the outbound plug of the window using the code below :
DATA: lr_window TYPE REF TO cl_bsp_wd_window,
        lv_collection TYPE REF TO IF_BOL_BO_COL.
lv_collection = me->typed_context->contextname->collection_wrapper.
lr_window = me->view_manager->get_window_controller( ).
lr_window->call_outbound_plug( iv_outbound_plug   = 'Windowoutboundplug name'
                                 iv_data_collection = lv_collection ).
and in the window outbound plug , fire that plug using the code
me->fire_outbound_plug('Windowoutboundplugname').
I had similar requirement and it worked.

How to populate a table based on a row selection from another table.

Hi, i just started to use ADF BC and Faces. Could some one help me or point me a solution on the following scenario .
By using a search component , a table is being displayed as a search result. If i select any row in the resulted table , i need to populate an another table at the bottom of the same page from another view. These two tables are related by primary key . May i know how to populate a table based on a row selection from another table. Thanks
ganesh

I understand your requirement and the tutorial doesn't talk about Association between the views so that you can create a Master-Detail or in DB parlance, a Parent-Child relationship.
I will assume that we are dealing with two entities here: Department and Employees where a particular Department has many Employees and hence a Parent-Child relationship.
Firstly, you need to create an Association between the two Entities - Department and Employees. You can do that by right clicking on the model's entity and then associating the two entities with the appropriate key say, DepartmentId.
Once you have done that, you need to link the two entities in the View section with this Association that you created. Then go to AppModule and make sure that in the Available View Objects: 'EmployeesView' appears under 'DepartmentView' as "EmployeesView via <link you created>". Shuttle the 'DepartmentView' to the right, Data Model and then shuttle
"EmployeesView via <link you created>" to the right, Data Model under 'DepartmentView'.
This will then be reflected in your Data Controls. After that, you simply would have to drag this View into your page as a Master-Detail form...and then when you run this page, any row selected in the Master table, would display the data in the Detail table.
Also, refer to this link: [Master-Detail|http://baigsorcl.blogspot.com/2010/03/creating-master-detail-form-in-adf.html]
Hope this helps.

Query returning unexpected results.

Hi,
One of our query which use to run successfully is suddenly failing in one of the environment. Oracle Version: 11.2.0.2.0. Can someone please suggest me why the query is not behaving as expected and works fine when using hint?
The below query doesn't return any rows.
select ctran.* from f_transaction_released tran, F_CHARGE_CODE_RELEASED CTRAN where
id_liability_cif in ('727873','141515') and TRAN.ID_TRANSACTION_RELEASED = CTRAN.ID_TRANSACTION_RELEASED The same query with hint return rows.
select /*+ optimizer_features_enable('9.2.0.8') */ ctran.* from f_transaction_released tran, F_CHARGE_CODE_RELEASED CTRAN where
id_liability_cif in ('727873','141515') and TRAN.ID_TRANSACTION_RELEASED = CTRAN.ID_TRANSACTION_RELEASED Explain plan of both the queries are:
1st Query:
Plan hash value: 196119809
| Id | Operation                                 | Name                       | Rows | Bytes | Cost (%CPU)| Time     | Pstart| Pstop |    TQ |IN-OUT| PQ Distrib |
|   0 | SELECT STATEMENT                          |                            |   750 | 96000 |   551   (1)| 00:00:07 |       |       |        |      |            |
|   1 | PX COORDINATOR                           |                            |       |       |            |          |       |       |        |      |            |
|   2 |   PX SEND QC (RANDOM)                     | :TQ10001                   |   750 | 96000 |   551   (1)| 00:00:07 |       |       | Q1,01 | P->S | QC (RAND) |
|* 3 |    HASH JOIN                              |                            |   750 | 96000 |   551   (1)| 00:00:07 |       |       | Q1,01 | PCWP |            |
|   4 |     BUFFER SORT                           |                            |       |       |            |          |       |       | Q1,01 | PCWC |            |
|   5 |      PX RECEIVE                           |                            |   444 | 5328 |   330   (0)| 00:00:04 |       |       | Q1,01 | PCWP |            |
|   6 |       PX SEND BROADCAST                   | :TQ10000                   |   444 | 5328 |   330   (0)| 00:00:04 |       |       |        | S->P | BROADCAST |
|   7 |        PARTITION RANGE ALL                |                            |   444 | 5328 |   330   (0)| 00:00:04 |     1 |    96 |        |      |            |
|   8 |         INLIST ITERATOR                   |                            |       |       |            |          |       |       |        |      |            |
|   9 |          TABLE ACCESS BY LOCAL INDEX ROWID| F_TRANSACTION_RELEASED     |   444 | 5328 |   330   (0)| 00:00:04 |     1 |    96 |        |      |            |
| 10 |           BITMAP CONVERSION TO ROWIDS     |                            |       |       |            |          |       |       |        |      |            |
|* 11 |            BITMAP INDEX SINGLE VALUE      | F_TRANSACTION_RELEASE_BMX9 |       |       |            |          |     1 |    96 |        |      |            |
| 12 |     PX BLOCK ITERATOR                     |                            | 7579K|   838M|   219   (1)| 00:00:03 |     1 |     3 | Q1,01 | PCWC |            |
|* 13 |      TABLE ACCESS FULL                    | F_CHARGE_CODE_RELEASED     | 7579K|   838M|   219   (1)| 00:00:03 |     1 |     3 | Q1,01 | PCWP |            |
Predicate Information (identified by operation id):
   3 - access("TRAN"."ID_TRANSACTION_RELEASED"="CTRAN"."ID_TRANSACTION_RELEASED")
11 - access("ID_LIABILITY_CIF"=141515 OR "ID_LIABILITY_CIF"=727873)
13 - filter(SYS_OP_BLOOM_FILTER(:BF0000,"CTRAN"."ID_TRANSACTION_RELEASED"))2nd query:
Plan hash value: 4037684686
| Id | Operation                                 | Name                       | Rows | Bytes | Cost | Pstart| Pstop |    TQ |IN-OUT| PQ Distrib |
|   0 | SELECT STATEMENT                          |                            |     2 |   256 |   299 |       |       |        |      |            |
|   1 | PX COORDINATOR                           |                            |       |       |       |       |       |        |      |            |
|   2 |   PX SEND QC (RANDOM)                     | :TQ10002                   |     2 |   256 |   299 |       |       | Q1,02 | P->S | QC (RAND) |
|* 3 |    HASH JOIN BUFFERED                     |                            |     2 |   256 |   299 |       |       | Q1,02 | PCWP |            |
|   4 |     BUFFER SORT                           |                            |       |       |       |       |       | Q1,02 | PCWC |            |
|   5 |      PX RECEIVE                           |                            |     1 |    12 |   203 |       |       | Q1,02 | PCWP |            |
|   6 |       PX SEND HASH                        | :TQ10000                   |     1 |    12 |   203 |       |       |        | S->P | HASH       |
|   7 |        PARTITION RANGE ALL                |                            |     1 |    12 |   203 |     1 |    96 |        |      |            |
|   8 |         INLIST ITERATOR                   |                            |       |       |       |       |       |        |      |            |
|   9 |          TABLE ACCESS BY LOCAL INDEX ROWID| F_TRANSACTION_RELEASED     |     1 |    12 |   203 |     1 |    96 |        |      |            |
| 10 |           BITMAP CONVERSION TO ROWIDS     |                            |       |       |       |       |       |        |      |            |
|* 11 |            BITMAP INDEX SINGLE VALUE      | F_TRANSACTION_RELEASE_BMX9 |       |       |       |     1 |    96 |        |      |            |
| 12 |     PX RECEIVE                            |                            | 7579K|   838M|    96 |       |       | Q1,02 | PCWP |            |
| 13 |      PX SEND HASH                         | :TQ10001                   | 7579K|   838M|    96 |       |       | Q1,01 | P->P | HASH       |
| 14 |       PX BLOCK ITERATOR                   |                            | 7579K|   838M|    96 |     1 |     3 | Q1,01 | PCWC |            |
| 15 |        TABLE ACCESS FULL                  | F_CHARGE_CODE_RELEASED     | 7579K|   838M|    96 |     1 |     3 | Q1,01 | PCWP |            |
Predicate Information (identified by operation id):
   3 - access("TRAN"."ID_TRANSACTION_RELEASED"="CTRAN"."ID_TRANSACTION_RELEASED")
11 - access("ID_LIABILITY_CIF"=141515 OR "ID_LIABILITY_CIF"=727873)
Note
   - cpu costing is off (consider enabling it)

Hence my questions, which you didn't address:
1) It might very well be a bug, did you check MetaLink/MyOracleSupport already?
I didn't check that yet'Suddenly failing' is often a synonym for 'something has changed'.
2)Are you absolutely sure nothing has changed?
Nothing has changed unless some stats or index got corrupted which we are assuming.3)What made you decide to use that hint anyway?
We read somewhere there is a bug with Oracle 11G hash joins and trying with 9i does help. 4)And are the tables 'normal, ordinary tables' or does the F_ prefix indicate something special?
It's fact tablesAnd to add another one:
5) Did you or your DBA noticed strange errors or messages in the alert.log?
Have to check on that.

About row selection in JTable

This is also a question about JTable, when type the key "ENTER", the row selection will focus on the next line, how can I stop this default action? Can I make the default action of pressing "ENTER" to be activate a cell in the JTable to editing state?
Thanks for any help.

Sorry, I need to ask for help again, yes, in your case, the method works,
but I am afraid this method does not help me, because I don't know HOW TO MAKE THE F2 FUNCTION in my case.
I use the method you recommend, and yes I can stop the default response of pressing ENTER, it means when I stroke ENTER in my table, the selection won't go to the next line, but it just up to my half purpose, how can I use Enter to editing a cell then? My silly question is I even don't know how to make F2 works?

Inconsistent SDO_RELATE results when querying 2.5D data

Oracle 11.1.0.7 with Patch 8343061 on Windows Server 2003 32bit.
I'm getting inconsistent results from SDO_RELATE results when querying 2.5D data. Some geometries I expect to be OVERLAPBDYDISJOINT, are not always being returned by SDO_RELATE when using the OVERLAPBDYDISJOINT mask. It seems that the order of the tables makes a difference to the result.
Here's a table with one 2.5D geometry and a 2D index:
CREATE TABLE TEST1 (
ID                NUMBER PRIMARY KEY,
GEOMETRY     SDO_GEOMETRY);
INSERT INTO TEST1 (id, geometry) VALUES (
1,
SDO_GEOMETRY(3002, 2157, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(561695.935, 834005.726, 25.865,
561696.229, 834005.955, 25.867, 561686.278, 834015.727, 26.088, 561685.179, 834019.771, 26.226, 561680.716, 834022.389, 26.226,
561674.434, 834025.125, 26.171, 561671.963, 834032.137, 25.667, 561670.832, 834037.185, 25.619, 561667.946, 834042.976, 25.84,
561666.717, 834047.218, 26.171, 561664.229, 834051.781, 26.778, 561660.041, 834055.935, 26.64, 561657.514, 834061.742, 26.53,
561658.59, 834067.116, 27.882, 561657.67, 834070.739, 28.821, 561653.028, 834073.777, 29.042, 561653.234, 834078.769, 28.379,
561658.336, 834080.105, 29.511, 561664.582, 834079.468, 31.94, 561669.257, 834075.821, 33.707, 561672.716, 834074.456, 33.707,
561676.875, 834077.262, 33.735, 561675.868, 834081.55, 33.707, 561673.131, 834087.641, 33.679, 561672.208, 834093.502, 33.238,
561668.578, 834100.894, 33.735, 561666.013, 834106.399, 33.679, 561661.408, 834111.23, 33.514, 561654.854, 834117.181, 33.486,
561651.695, 834122.292, 33.569, 561649.112, 834128.847, 33.431, 561645.982, 834134.786, 33.293, 561642.485, 834141.235, 33.072,
561642.138, 834150.085, 33.293, 561646.072, 834159.721, 36.578, 561647.274, 834165.532, 37.02, 561646.359, 834170.867, 37.02,
561645.42, 834175.485, 36.799, 561642.44, 834180.977, 36.826, 561638.677, 834185.419, 36.771, 561636.693, 834194.824, 37.158,
561635.462, 834202.105, 37.241, 561631.998, 834208.745, 37.268, 561628.871, 834213.994, 37.241, 561627.554, 834220.393, 37.82,
561625.79, 834226.697, 39.532, 561620.561, 834236.494, 39.891, 561619.265, 834249.687, 39.697, 561619.883, 834260.02, 41.326,
561620.977, 834264.399, 43.093, 561622.557, 834270.723, 43.452, 561622.172, 834276.978, 43.452, 561621.347, 834285.541, 43.479,
561622.214, 834292.055, 43.645, 561619.718, 834302.583, 43.755, 561616.762, 834316.47, 43.755, 561608.842, 834328.241, 43.7,
561606.346, 834334.93, 43.7, 561605.27, 834341.929, 43.7, 561603.925, 834350.648, 43.728, 561602.462, 834358.405, 43.838,
561599.552, 834366.629, 44.031, 561594.551, 834374.291, 43.396, 561590.644, 834383.986, 43.065, 561588.48, 834392.21, 44.942,
561586.923, 834397.32, 46.737, 561584.608, 834402.898, 49.299, 561581.389, 834410.194, 50.077, 561580.437, 834419.49, 51.907,
561580.438, 834427.63, 53.127, 561582.245, 834433.389, 55.791, 561586.664, 834433.397, 57.503, 561593.88, 834433.608, 57.475,
561596.305,834439.653, 57.42, 561591.804, 834445.862, 57.309, 561589.097, 834447.689, 57.014)));
SELECT sdo_geom.validate_geometry_with_context(geometry, 0.0005) FROM TEST1;
DELETE FROM user_sdo_geom_metadata WHERE table_name = 'TEST1' AND column_name = 'GEOMETRY';
INSERT INTO user_sdo_geom_metadata VALUES ('TEST1','GEOMETRY',
     MDSYS.SDO_DIM_ARRAY(
     MDSYS.SDO_DIM_ELEMENT('X',400000,750000,0.0005),
     MDSYS.SDO_DIM_ELEMENT('Y',500000,1000000,0.0005),
     MDSYS.SDO_DIM_ELEMENT('Z',-10000,10000,0.0005)
), 2157);
DROP INDEX TEST1_SPIND;
CREATE INDEX TEST1_SPIND ON TEST1(GEOMETRY) INDEXTYPE IS MDSYS.SPATIAL_INDEX PARAMETERS ('layer_gtype=line sdo_indx_dims=2');And here's another table with a 2D geometry and a 2D index:
CREATE TABLE TEST2 (
ID                NUMBER PRIMARY KEY,
GEOMETRY     SDO_GEOMETRY);
INSERT INTO TEST2 (id, geometry) VALUES (
1,
SDO_GEOMETRY(2002, 2157, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(561816.516, 834055.581, 561819.504, 834057.173,
561817.942, 834060.818, 561810.044, 834078.997, 561805.576, 834087.634, 561801.572, 834094.299, 561798.558, 834100.467,
561796.254, 834107.637, 561793.754, 834115.605, 561794.049, 834123.694, 561793.698, 834130.518, 561792.905, 834138.883,
561787.867, 834145.772, 561782.544, 834150.548, 561777.707, 834156.53, 561773.945, 834161.32, 561771.061, 834166.957,
561768.155, 834173.131, 561764.735, 834178.744, 561759.603, 834187.782, 561756.146, 834195.493, 561753.416, 834198.821,
561754.141, 834205.691, 561756.768, 834209.681, 561757.217, 834216.701, 561753.086, 834232.46, 561744.371, 834254.589,
561740.936, 834263.001, 561737.198, 834272.208, 561732.231, 834284.915, 561730.52, 834297.01, 561728.339, 834310.053,
561727.825, 834328.069, 561730.461, 834342.992, 561729.808, 834367.948, 561730.216, 834396.988, 561732.273, 834419.047,
561732.783, 834424.668, 561731.647, 834432.212, 561731.872, 834439.436, 561731.39, 834449.269, 561732.041, 834462.813,
561733.583, 834471.926, 561733.229, 834485.049, 561730.868, 834498.462, 561726.379, 834512.59, 561725.776, 834528.932,
561727.488, 834555.23, 561729.357, 834577.873, 561731.05, 834595.931, 561731.163, 834611.928, 561734.057, 834637.031,
561732.67, 834636.4, 561725.401, 834633.796, 561721.039, 834632.493, 561718.777, 834632.167, 561710.437, 834632.888,
561647.929, 834636.658, 561644.963, 834630.085, 561632.796, 834629.813, 561625.553, 834627.647, 561620.473, 834626.711,
561608.718, 834624.94, 561599.935, 834619.684, 561596.67, 834613.843, 561594.27, 834607.774, 561592.513, 834601.752,
561591.349, 834593.899, 561597.265, 834584.888, 561595.956, 834571.479, 561595.075, 834556.196, 561593.997, 834539.68,
561594.316, 834528.071, 561595.261, 834516.44, 561595.538, 834504.804, 561597.227, 834497.417, 561599.3, 834490.416,
561601.265, 834482.61, 561605.126, 834475.502, 561599.232, 834473.683, 561593.076, 834471.379, 561599.154, 834451.112,
561589.097, 834447.689, 561591.804, 834445.862, 561596.305, 834439.653, 561593.88, 834433.608, 561582.245, 834433.389,
561580.438, 834427.63, 561580.437, 834419.49, 561581.389, 834410.194, 561584.608, 834402.898, 561586.923, 834397.32,
561588.48, 834392.21, 561590.644, 834383.986, 561594.551, 834374.291, 561599.552, 834366.629, 561602.462, 834358.405,
561603.925, 834350.648, 561605.27, 834341.929, 561606.346, 834334.93, 561608.842, 834328.241, 561616.762, 834316.47,
561619.718, 834302.583, 561622.214, 834292.055, 561621.347, 834285.541, 561622.172, 834276.978, 561622.557, 834270.723,
561620.977, 834264.399, 561619.883, 834260.02, 561619.265, 834249.687, 561620.561, 834236.494, 561625.79, 834226.697,
561627.554, 834220.393, 561628.871, 834213.994, 561631.998, 834208.745, 561635.462, 834202.105, 561636.693, 834194.824,
561638.677, 834185.419, 561642.44, 834180.977, 561645.42, 834175.485, 561646.359, 834170.867, 561647.274, 834165.532,
561646.072, 834159.721, 561642.138, 834150.085, 561642.485, 834141.235, 561645.982, 834134.786, 561649.112, 834128.847,
561651.695, 834122.292, 561654.854, 834117.181, 561661.408, 834111.23, 561666.013, 834106.399, 561668.578, 834100.894,
561672.208, 834093.502,561673.131, 834087.641, 561675.868, 834081.55, 561676.875, 834077.262, 561672.716, 834074.456,
561669.257, 834075.821, 561664.582, 834079.468, 561658.336, 834080.105, 561653.234, 834078.769, 561653.028, 834073.777,
561657.67, 834070.739, 561658.59, 834067.116, 561657.514, 834061.742, 561660.041, 834055.935, 561664.229, 834051.781,
561666.717, 834047.218, 561667.946, 834042.976, 561670.832, 834037.185, 561671.963, 834032.137, 561674.434, 834025.125,
561680.716, 834022.389, 561685.179, 834019.771, 561686.278, 834015.727, 561696.229, 834005.955, 561695.935, 834005.726,
561677.805, 833994.91, 561683.163, 833985.817, 561703.01, 833949.434, 561725.891, 833961.856, 561744.35, 833971.197,
561768.396, 833983.86, 561777.842, 833988.883, 561798.333, 833999.743, 561797.243, 834005.725, 561783.574, 834040.515,
561798.127, 834046.391, 561807.001, 834050.509, 561816.516, 834055.581)));
SELECT sdo_geom.validate_geometry_with_context(geometry, 0.0005) FROM TEST2;
DELETE FROM user_sdo_geom_metadata WHERE table_name = 'TEST2' AND column_name = 'GEOMETRY';
INSERT INTO user_sdo_geom_metadata VALUES ('TEST2','GEOMETRY',
     MDSYS.SDO_DIM_ARRAY(
     MDSYS.SDO_DIM_ELEMENT('X',400000,750000,0.0005),
     MDSYS.SDO_DIM_ELEMENT('Y',500000,1000000,0.0005)
), 2157);
DROP INDEX TEST2_SPIND;
CREATE INDEX TEST2_SPIND ON TEST2(GEOMETRY) INDEXTYPE IS MDSYS.SPATIAL_INDEX PARAMETERS ('layer_gtype=line sdo_indx_dims=2');Now if I check how these two geometries relate to each other, the answer is OVERLAPBDYDISJOINT, which makes sense when inspecting the geometries.
SQL> SELECT
2 sdo_geom.relate(t1.geometry, 'determine', t2.geometry, 0.0005) relate_1_to_2,
3 sdo_geom.relate(t2.geometry, 'determine', t1.geometry, 0.0005) relate_2_to_1
4 FROM test2 t2, test1 t1
5 WHERE t1.id = t2.id;
RELATE_1_TO_2        RELATE_2_TO_1
OVERLAPBDYDISJOINT   OVERLAPBDYDISJOINT
1 row selected.So, I'd expect this query to return something...
SELECT /*+ ORDERED */ t1.id, t2.id, sdo_geom.relate(t1.geometry, 'determine', t2.geometry, 0.0005) relate
FROM test2 t2, test1 t1
WHERE sdo_relate(t1.geometry, t2.geometry, 'mask=overlapbdydisjoint') = 'TRUE'
AND t1.id = 1
AND t2.id = 1;Nada. And this...
SELECT /*+ ORDERED */ t1.id, t2.id, sdo_geom.relate(t1.geometry, 'determine', t2.geometry, 0.0005) relate
FROM test1 t1, test2 t2
WHERE sdo_relate(t2.geometry, t1.geometry, 'mask=overlapbdydisjoint') = 'TRUE'
AND t1.id = 1
AND t2.id = 1;Nada.
And this...
SQL> SELECT /*+ ORDERED */ t1.id, t2.id, sdo_geom.relate(t1.geometry, 'determine', t2.geometry, 0.0005) relate
2 FROM test2 t2, test1 t1
3 WHERE sdo_relate(t2.geometry, t1.geometry, 'mask=overlapbdydisjoint') = 'TRUE'
4 AND t1.id = 1
5 AND t2.id = 1;
        ID         ID RELATE
         1          1 OVERLAPBDYDISJOINT
1 row selected.This version gives the right answer.
Can anyone explain this?

Hi,-
I think you are running into these bugs 7158518 and 7710726.
Could you please request the patch for the bugs so that they are published on Metalink
if they dont exist there?
Please let us know if these fix your problem.
Best regards
baris

Getting different behaviour when query hits a single row?

Hi
I have a page where people type in search conditions and when they see the results (an ordinary tabluar report) they can click a certain row to assign the key of that row to a hidden field in my page.
There's a requirement that if they're clever enough to hit a single matching row, then the key of that row is assigned to my hidden item without them having to go through the stress and hard work related to clicking a link :-)
So I'll probably make a process that tests to see if their search returns a single row and only do the report if not. But that means performing the resulting SQL twice when there's more than one row.
Is there a way to have the number of rows returned by the SQL source for a report affect the behaviour of the page? AFAIK the #TOTAL_ROWS# etc. are only applicable in the header & footer of the report region, so I guess there's no way to do what I imagined?
Jakob

You could query your rows into a collection and determine the number of records in the collection. Check out the HTMLDB_COLLECTION (APEX_COLLECTION) API section in the HTML DB (APEX) documentation.
Your multiple record region where they select their row could then be based on:
SELECT * FROM HTMLDB_COLLECTION WHERE collection_name = 'my collection'
Mike

Displaying a message when there are no results from an XSL Query

Using MM_XSLTransform.class.php
I am querying an XML file to produce a list of places whose town name or address match a letter of the alphabet. The letter is passed as a variable in a URL.
XSL:
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<xsl:param name="letter"/>
<xsl:output method="html" encoding="UTF-8"/>
<xsl:template match="/">
<xsl:for-each select="dataroot/CPINFOWEB[Town=starts-with(Town, $letter) or Name=starts-with(Name, $letter)]">
      <table width="100%" border="0" cellspacing="0" cellpadding="0">
        <tr>
        <td>
    <a href="detail.php?park={CostCode}"><xsl:value-of select="Name"/></a><br />
          <a href="detail.php?park={CostCode}"><xsl:value-of select="Town"/></a><br />
      <xsl:value-of select="Address"/><br />
      <br />
      </td>
        </tr>
      </table>
      </xsl:for-each>
</xsl:template>
</xsl:stylesheet>
Destination PHP file:
setXML("../regions/CPINFOWEB-mobile.xml"); $mm_xsl->setXSL("list.xsl"); $mm_xsl->addParameter("letter",$_GET['letter']); echo $mm_xsl->Transform(); ?>
The result Name and Town are displayed as a URL to link to a "more details" page.
All works fine, but when there are no results for a letter of the alphabet I obviously get a blank page.
How do I display a "no results" message instead

I deleted my original reply because the formatting of the XSL code was messed up by the forum. Here's trying again:
Your current code creates a new table for each result. The opening and closing <table> tags should be outside the the <for-each> loop. To deal with the possibility of no results being found, use a conditional statement and the count() function like this:
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<xsl:param name="letter"/>
<xsl:output method="html" encoding="UTF-8"/>
<xsl:template match="/">
<table width="100%" border="0" cellspacing="0" cellpadding="0">
<xsl:for-each select="dataroot/CPINFOWEB[Town=starts-with(Town, $letter) or Name=starts-with(Name, $letter)]">
        <tr>
        <td>
    <a href="detail.php?park={CostCode}"><xsl:value-of select="Name"/></a><br />
          <a href="detail.php?park={CostCode}"><xsl:value-of select="Town"/></a><br />
      <xsl:value-of select="Address"/><br />
      <br />
      </td>
        </tr>
</xsl:for-each>
<xsl:if test="count(dataroot/CPINFOWEB/Town) &lt; 1">
    <tr>
    <td>No records found</td>
    </tr>
    </xsl:if>
</table>
</xsl:template>
</xsl:stylesheet>

Obtaining "rows selected" value after custom sql query in Database adaptor

We are executing a custom query in a database adaptor. With other technologies (JDBC, etc.) the result of a query will not only produce a result set but a count of the number of rows selected. E.G. the script output of Oracle SQL Developer will print out something like:
9999 rows selected
at the end of the script output.
I would like to obtain this value for a BPEL process. Of course, I could execute a 2nd query whose where clause is identical to the first, but selects count(*) instead. However, this is not only inefficient but (in rare circumstances in an active database) could be wrong.
It is not obvious to this BPEL novice how to obtain the row selected value as well as the result set in one Invoke. Is this possible?

This may not be the only solution - but it is how I have done it in the past.
Following the invoke step of the adapter, use an assign/copy step to populate an integer BPEL variable using the count xpath function...
<assign name="Initialize">
<copy>
<from expression="count(bpws:getVariableData('Invoke_Query_OutputVariable','MyTableQueryCollection','/ns3:MyTableQueryCollection/ns3:MyTableQuery'))"/>
<to variable="NumberOfRecordsReturned"/>
</copy>
</assign>
That should assign the number of records returned by the query.
I hope that helps.
Rod.
Edited by: Rod Tunnels on Dec 15, 2009 1:16 PM

Sysdate changes when number of rows selected are huge

My requirement is that same date and time should be selected for all the rows returned by the query.
Eg: Select empno, ename , sysdate from Emp
If the query runs for more than a second, then the second component of SYSDATE will be different.
What I want is that the query firing time should be selected for all the rows returned by the query.
I hope there should be a way in Oracle to do this

Have you actually seen this happen?
On testing in Oracle 8.1.7i environment with a query
select col1, col2, to_char(sysdate,'hh24:mi:ss')
from big_table;
which returned approx 3m rows and executed for over 8 minutes the sysdate value was the same for the first row selected and the last row selected, and was the time at the start of the query.
Kevin is correct that Oracle gets the the value of Sysdate once when the query is executed and uses that value until the time that a new query is parsed.
HTH
Dave

Selecting first N characters when querying the CMS

I am trying to retrieve only the first 6 characters of the SI_KEYWORDS field when querying the CMS from within the SDK. When testing within QueryBuilder the following in bold does not work, although LEFT is a command for achieving this in SQL. Can someone help me to know if this is possible within QueryBuilder SQL and if so how to achieve it?
Select LEFT(SI_KEYWORD,6) as keyword, SI_NAME From CI_INFOOBJECTS, CI_SYSTEMOBJECTS, CI_APPOBJECTS WHere SI_KIND='webi'
and SI_KEYWORD != '' and SI_KEYWORD != 'Hidden' and SI_KEYWORD != 'Auditor'
ORDER BY keyword, SI_NAME
Thanks,
Dave

Hi Ted,
Thanks for your reply. I understand the querying of the CMS better after reading it.
We are utilizing the keywords field and the description field to obtain some metadata about our reports that I need to access from java code. Unfortunately, we have 4 different pieces of metadata we want to store and only the 2 fields in which to store them, so we are using delimiters in the keywords field to separate the values. For example, we have "value1value2" as the keyword field in one report, but in another report if value2 is blank we simply have "value1". This works well as we just parse the delimiters in java and we can store the 2 different values in the one keyword field. The part that is not working well with this approach, though, is ordering the results. We want to order the reports by value1 and then by SI_NAME. Because some of the reports have value1value2 and others just have value1 it throws this ordering off if I use "ORDER BY SI_KEYWORD, SI_NAME".
I've been looking for ways to get around this without doing a re-sort in Java and this is all I could think of:
1. Are there some additional user-defined fields that we could expose in the report properties in the CMC, and then retrieve via Query Builder / SDK? Something like SI_UDF1, SI_UDF2, etc. All we could find were keywords and description.
2. Using a SUBSTR or LEFT-like function on the keywords field so that it only gets value1 for sorting purposes only, but still retrieve the entire keywords field in the SELECT. I understand now based on your explanation that this will not work as (if I understand correctly) it would modify the report object in the CMS to set the keyword to the truncated value.
Any advice you could offer would be greatly appreciated. I know I can always bite the bullet and do the sorting java-side once I get the resultset back, but I was hoping to avoid the performance hit of doing that.
Thanks,
Dave

No rows selected even when SELECT granted.

I have a view that I created in OEM 12c owned by SYSMAN. The view is the following:
create or replace view chk_dbmango as
SELECT LOWER (a_size.target_name) target_name,
         tphost.host_name,
         tpba.business_area,
         tpd.contact,
         tpapp.application,
         tpenv.environment,
         ROUND (AVG (a_size.size_gb), 2) SIZE_GB,
         ROUND (AVG (a_size.used_gb), 2) USED_GB,
         ROUND (AVG (a_size.size_gb - a_size.used_gb), 2) FREE_GB,
         ROUND (AVG ((a_size.used_gb * 100) / DECODE (a_size.size_gb, 0, 1, a_size.size_gb))) USED_PCT
    FROM ( SELECT t.target_name,
                   t.target_guid,
                   SUM (d.tablespace_size) / 1024 / 1024 / 1024 size_gb,
                   SUM (d.tablespace_used_size) / 1024 / 1024 / 1024 used_gb
              FROM sysman.mgmt$db_tablespaces d, sysman.mgmt$target_type t
             WHERE (t.target_type = 'rac_database'
                OR (t.target_type = 'oracle_database'
               AND t.TYPE_QUALIFIER3 <> 'RACINST'))
               AND d.target_name(+) = t.target_name
               AND t.metric_name = 'tbspAllocation'
               AND (t.metric_column = 'spaceAllocated')
          GROUP BY t.target_name, t.target_guid, t.metric_column) a_size,
         ( SELECT property_value AS host_name,
                   target_guid
              FROM sysman.mgmt$target_properties
             WHERE property_name = 'MachineName') tphost,
         (   SELECT property_value AS business_area,
                    target_guid
               FROM sysman.mgmt$target_properties
              WHERE property_name = 'orcl_gtp_line_of_bus') tpba,
         (   SELECT property_value AS contact,
                    target_guid
               FROM sysman.mgmt$target_properties
              WHERE property_name = 'orcl_gtp_contact') tpd,
         (   SELECT property_value AS application,
                    target_guid
               FROM sysman.mgmt$target_properties
              WHERE property_name = 'orcl_gtp_comment') tpapp,
         (   SELECT property_value AS environment,
                    target_guid
               FROM sysman.mgmt$target_properties
              WHERE property_name = 'orcl_gtp_deployment_type') tpenv
   WHERE a_size.target_guid = tphost.target_guid
     AND a_size.target_guid = tpba.target_guid(+)
     AND a_size.target_guid = tpd.target_guid(+)
     AND a_size.target_guid = tpapp.target_guid(+)
     AND a_size.target_guid = tpenv.target_guid(+)
GROUP BY a_size.target_name,
         tphost.host_name,
         tpba.business_area,
         tpd.contact,
         tpapp.application,
         tpenv.environment
ORDER BY 1;
I granted SELECT on this view to user svcmango. When connected as svcmango and query the view, I get no rows selected. Connected as sysman I get 99 rows. There must be something simple that I have overlooked. Please help. Thanks.

Here are the steps taken:
OMS12C> conn SYSMAN
Enter password:
Connected.
OMS12C> create or replace view chk_dbmango as
SELECT LOWER (a_size.target_name) target_name,
         tphost.host_name,
         tpba.business_area,
         tpd.contact,
         tpapp.application,
         tpenv.environment,
         ROUND (AVG (a_size.size_gb), 2) SIZE_GB,
         ROUND (AVG (a_size.used_gb), 2) USED_GB,
         ROUND (AVG (a_size.size_gb - a_size.used_gb), 2) FREE_GB,
         ROUND (AVG ((a_size.used_gb * 100) / DECODE (a_size.size_gb, 0, 1, a_size.size_gb))) USED_PCT
    FROM ( SELECT t.target_name,
                   t.target_guid,
                   SUM (d.tablespace_size) / 1024 / 1024 / 1024 size_gb,
                   SUM (d.tablespace_used_size) / 1024 / 1024 / 1024 used_gb
              FROM sysman.mgmt$db_tablespaces d, sysman.mgmt$target_type t
             WHERE (t.target_type = 'rac_database'
                OR (t.target_type = 'oracle_database'
               AND t.TYPE_QUALIFIER3 <> 'RACINST'))
               AND d.target_name(+) = t.target_name
               AND t.metric_name = 'tbspAllocation'
               AND (t.metric_column = 'spaceAllocated')
          GROUP BY t.target_name, t.target_guid, t.metric_column) a_size,
         ( SELECT property_value AS host_name,
                   target_guid
              FROM sysman.mgmt$target_properties
             WHERE property_name = 'MachineName') tphost,
         (   SELECT property_value AS business_area,
                    target_guid
               FROM sysman.mgmt$target_properties
              WHERE property_name = 'orcl_gtp_line_of_bus') tpba,
         (   SELECT property_value AS contact,
                    target_guid
               FROM sysman.mgmt$target_properties
              WHERE property_name = 'orcl_gtp_contact') tpd,
         (   SELECT property_value AS application,
                    target_guid
               FROM sysman.mgmt$target_properties
              WHERE property_name = 'orcl_gtp_comment') tpapp,
         (   SELECT property_value AS environment,
                    target_guid
               FROM sysman.mgmt$target_properties
              WHERE property_name = 'orcl_gtp_deployment_type') tpenv
   WHERE a_size.target_guid = tphost.target_guid
     AND a_size.target_guid = tpba.target_guid(+)
     AND a_size.target_guid = tpd.target_guid(+)
     AND a_size.target_guid = tpapp.target_guid(+)
     AND a_size.target_guid = tpenv.target_guid(+)
GROUP BY a_size.target_name,
         tphost.host_name,
         tpba.business_area,
         tpd.contact,
         tpapp.application,
         tpenv.environment
ORDER BY 1;
2    3    4    5    6    7    8    9   10   11   12   13   14   15   16   17   18   19   20   21   22   23   24   25   26   27   28   29   30   31   32   33   34   35   36   37   38   39   40   41   42   43   44   45   46   47   48   49   50   51   52   53   54   55
View created.
Elapsed: 00:00:00.04
OMS12C> select count(*) from chk_dbmango;
COUNT(*)
        99
1 row selected.
Elapsed: 00:00:00.48
OMS12C> grant select on chk_dbmango to svcdbmango;
Grant succeeded.
Elapsed: 00:00:00.01
OMS12C> conn svcdbmango
Enter password:
Connected.
OMS12C> select count(*) from sysman.chk_dbmango;
COUNT(*)
         0
1 row selected.
Elapsed: 00:00:00.73
OMS12C>

Stop executing query once the result is more than n rows

Hi,
Is it possible to stop executing a query for a View Object once the result hits n rows?
Any pointers are appreciated
Thank you for your time.
Edited by: user594688 on Sep 12, 2008 8:21 AM

Rownum is indeed the attribute. If you really want to stop the query after the first n rows, that's pretty much the only way to do it, to my knowledge.
If you're primarily worried about database load, but want to give the user the option to query more rows if and when they really need them, check out the following in the Fusion Dev Guide for Forms/4GL developers:
37.1.5 Efficiently Scrolling Through Large Result Sets Using Range Paging
(Note that this is not the same as simply using a range size, which ADF does by default--the range size simply limits the number of rows displayed ot the user, not the number queried. It's also not the same as setting the JDBC Fetch size, which limits the number of rows loaded into the cache, and therefore onto the app server, at one time, but again not the actual query result.)

Issue with Selection Listener when the table has only one row

Hi All ,
I have developed a table in which I am using Selection Listener to perform some task when any row is selected.
It is working fine when I have more than 1 row in the table, but when I have only one row in the table , the selection listener do not call the corresponding method in bean.
I understand that selection event will be raised only when the row is changed, but in the use case when only one row is there, what should be done to make the selection listener work ?
In the selection listener I have written code to make the selected row as current row , and perform the required task.
Please suggest a way out for this situation.
Thanks in advance.

Hi,
try removing this attr from table
selectedRowKeys="#{bindings.xxx_VO1.collectionModel.selectedRow}"

Count the number of rows resulting from a select statement

Hi,
Is there any way of counting the number of rows resulting from a select statement. i.e I have a select distinct statement and I then want to perform an IF statement on the number of rows resulting from the select statement.
Any help appreciated
Thanks
Gary

Declare
var1 number;
Begin
select count(distinct column_name) into
var1 from table_name;
If var1 > x Then
End IF;
End;
Hope I understood the problem correctly
null

When queried v$dataguard_stats results no rows selected at standby db?

Similar Messages

Maybe you are looking for