Corrupted Query

Hello, I am having an issue with deleting my query. It was created in 7.0 QD. Now when I try to open it up it won't open and asks to close the QD. I then tried to delete is in RSZDELETE and got the following message:
"Query object D4KOG9TVDIFBUXABDH8MSQJ02 is blocked. Deletion has been cancelled."
Query Object is the query itself.
This is in DEV. I saw a couple of posts but no one really posted a solution for this. I even tried to go into RSREPDIR and tried to delete it from there. It said it got deleted but I am still not able save another query with this name.
Let me know if anyone has a solution.
Thanks, Syed.

Just to add. I went through all the tables and delete this name "D4KOG9TVDIFBUXABDH8MSQJ02" manually. There is a table for reference
RSZELTXREF
in which I see about 24 entries with this same technical names, under Layout type of element they are defined as VAR, SHT, SOB. I am hesitent to delete these entries. Does anyone know what they are.
Each of these entries has a different TELTUID name though.
Thanks,
Syed.

Similar Messages

Corrupted query witdh dataadapter.fill?

After using the ODP.NET driver (both) 9.2.0.4 and 9.2.0.2.102 for a while, we hit a problem today on 2 clients simulaneuously (new in-dev code, so maybe due to a recent change in our code).
The strange thing that happened (seen in sqlnet trace file) is that the query is transmitted with a corrupted character: the query is below. Note the '^' in 'part^source'. Should have been 'part_source'. Altough there are some things added dynamically to the query, the 'part_source' part is hardcoded. Has anyone seen something like this using ODP.NET?
Full query here:
SELECT part_no , description , base_uom , part^source , base_conv_factor , base_to_unit , part_type , date_imported , changed_date , alt_part_no , obsolete FROM part WHERE (part_no =:1) ORDER BY part_no ASC
Executed using:
' Create the DataAdapter & DataSet
lDa = New OracleDataAdapter(lCmd)
' Fill the DataSet using default
' values for DataTable names, etc.
lDa.Fill(lDt)
If aWithSchema = True Then
lDa.MissingSchemaAction = MissingSchemaAction.Add
lDa.FillSchema(lDt, SchemaType.Source)
End If

Below is the ODP.NET trace...
cirumstances:
we have a library of queries (datalayer) that are being called from within an ASP.NET app. The queries work fine for a while, but after some time a couple of queries get garbled in the DA.Fill. In the debugger, the query still looks find up till the moment of DA.Fill, but then the column 'part_source' becomes 'part^source'. There are manipulations with stringbuilder before that, but this part of the query is fixed in our code.
We have an operational version of our software running without this problem (but still on Framework 1.0, now we are at Framework 1.1). We have it both with 9.2.0.2102 and 9.2.0.4 ODP.NET vs. 9.2.0.1 Oracle DB (but since it's the Network send, I guess the target DB does not play a role in this problem).
Recreating this problem in a small testcase is not obvious as the same rahter generic code works for 100's of other queries without problems (even with the query that generates an issue). The problem goes away after iisreset.
TIME:2004/ 4/13-10:35:27: 6 TID: 768 OpsSqlExecuteNonQuery(): SQL: select parameter_data from interspc_cfg where section='interspec' and parameter='webversion'
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (EXIT) OpsSqlExecuteReader(): RetCode=0 Line=312
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (ENTRY) OpsSqlAllocValCtx()
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (EXIT) OpsSqlAllocValCtx(): RetCode=0 Line=137
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (ENTRY) OpsMetCopyValCtx()
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (EXIT) OpsMetCopyValCtx(): RetCode=0 Line=263
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (ENTRY) OpsErrAllocCtx()
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (EXIT) OpsErrAllocCtx(): RetCode=0 Line=185
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (ENTRY) OpsDacAllocValCtx()
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (EXIT) OpsDacAllocValCtx(): RetCode=0 Line=241
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (EXIT) OracleCommand::ExecuteReader()
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (ENTRY) OracleDataReader::Read()
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (ENTRY) OpsDacRead()
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (EXIT) OpsDacRead(): RetCode=0 Line=187
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (EXIT) OracleDataReader::Read()
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (EXIT) OracleCommand::ExecuteScalar()
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (ENTRY) OracleDataReader::GetValue()
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (ENTRY) OracleDataReader::IsDBNull()
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (ENTRY) OpsDacGetInd()
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (EXIT) OpsDacGetInd(): RetCode=0 Line=566
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (EXIT) OracleDataReader::IsDBNull()
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (ENTRY) OracleDataReader::GetString()
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (ENTRY) OpsDacGetType()
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (EXIT) OpsDacGetType(): RetCode=0 Line=685
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (EXIT) OracleDataReader::GetString()
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (EXIT) OracleDataReader::GetValue()
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (ENTRY) OpsDacDispose()
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (ENTRY) OpsDacFreeCtx()
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (EXIT) OpsDacFreeCtx(): RetCode=0 Line=353
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (ENTRY) OpsDacFreeValCtx()
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (EXIT) OpsDacFreeValCtx(): RetCode=0 Line=289
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (ENTRY) OpsErrFreeCtx()
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (EXIT) OpsErrFreeCtx(): RetCode=0 Line=212
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (ENTRY) OpsSqlFreeCtx()
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (EXIT) OpsSqlFreeCtx(): RetCode=0 Line=105
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (ENTRY) OpsSqlFreeValCtx()
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (EXIT) OpsSqlFreeValCtx(): RetCode=0 Line=154
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (ENTRY) OpsMetFreeValCtx()
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (EXIT) OpsMetFreeValCtx(): RetCode=0 Line=131
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (EXIT) OpsDacDispose(): RetCode=0 Line=438
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (ENTRY) OracleParameterCollection::Clear()
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (EXIT) OracleParameterCollection::Clear()
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (ENTRY) OpsSqlFreeValCtx()
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (EXIT) OpsSqlFreeValCtx(): RetCode=0 Line=154
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (ENTRY) OpsErrFreeCtx()
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (EXIT) OpsErrFreeCtx(): RetCode=0 Line=212
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (ENTRY) OracleParameter::OracleParameter(2)
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (ENTRY) OpsPrmAllocValCtx()
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (EXIT) OpsPrmAllocValCtx(): RetCode=0 Line=131
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (EXIT) OracleParameter::OracleParameter(2)
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (ENTRY) OracleCommand::OracleCommand(1)
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (EXIT) OracleCommand::OracleCommand(1)
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (ENTRY) OracleCommand::CommandText(): set
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (EXIT) OracleCommand::CommandText(): set
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (ENTRY) OracleParameterCollection::Add(2)
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (EXIT) OracleParameterCollection::Add(2)
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (ENTRY) OracleDataAdapter::OracleDataAdapter(2)
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (EXIT) OracleDataAdapter::OracleDataAdapter(2)
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (ENTRY) OpsPrmResetValCtx()
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (EXIT) OpsPrmResetValCtx(): RetCode=0 Line=154
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (ENTRY) OpsSqlExecuteReader()
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (ENTRY) OpsErrAllocCtx()
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (EXIT) OpsErrAllocCtx(): RetCode=0 Line=185
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (ENTRY) OpsSqlAllocCtx()
TIME:2004/ 4/13-10:35:27: 16 TID: 768 (EXIT) OpsSqlAllocCtx(): RetCode=0 Line=80
TIME:2004/ 4/13-10:35:27: 16 TID: 768 OpsSqlExecuteNonQuery(): SQL: SELECT part_no , description , base_uom , part^source , base_conv_factor , base_to_unit , part_type , date_imported , changed_date , alt_part_no , obsolete FROM part WHERE (part_no =:1) ORDER BY part_no ASC
TIME:2004/ 4/13-10:35:27: 36 TID: 768 (EXIT) OpsSqlExecuteReader(): RetCode=-1 Line=308
TIME:2004/ 4/13-10:35:27: 46 TID: 768 (ENTRY) OpsErrGetOpoCtx()
TIME:2004/ 4/13-10:35:27: 46 TID: 768 (ERROR) Oracle error code=923
TIME:2004/ 4/13-10:35:27: 46 TID: 768 (EXIT) OpsErrGetOpoCtx(): RetCode=0 Line=125
TIME:2004/ 4/13-10:35:36:941 TID: 768 (ENTRY) OracleConnection::Close()
TIME:2004/ 4/13-10:35:36:941 TID: 768 (ENTRY) OpsConClose()
TIME:2004/ 4/13-10:35:36:961 TID: 768 (EXIT) OpsConClose(): RetCode=0 Line=562
TIME:2004/ 4/13-10:35:36:961 TID: 768 (EXIT) OracleConnection::Close()
TIME:2004/ 4/13-10:35:36:961 TID: 768 (ENTRY) OracleConnection::Dispose()
TIME:2004/ 4/13-10:35:36:961 TID: 768 (ENTRY) OpsConDispose()
TIME:2004/ 4/13-10:35:36:961 TID: 768 (ENTRY) OpsConFreeValCtx()
TIME:2004/ 4/13-10:35:36:961 TID: 768 (EXIT) OpsConFreeValCtx(): RetCode=0 Line=587
TIME:2004/ 4/13-10:35:36:961 TID: 768 (EXIT) OpsConDispose(): RetCode=0 Line=697
TIME:2004/ 4/13-10:35:36:961 TID: 768 (EXIT) OracleConnection::Dispose()
TIME:2004/ 4/13-10:35:42:330 TID: 768 (ENTRY) OracleConnection::OracleConnection(2)
TIME:2004/ 4/13-10:35:42:330 TID: 768 (EXIT) OracleConnection::OracleConnection(2)
TIME:2004/ 4/13-10:35:42:330 TID: 768 (ENTRY) OracleConnection::Open()
TIME:2004/ 4/13-10:35:42:330 TID: 768 (ENTRY) OpsConAllocValCtx()
TIME:2004/ 4/13-10:35:42:330 TID: 768 (EXIT) OpsConAllocValCtx(): RetCode=0 Line=129
TIME:2004/ 4/13-10:35:42:330 TID: 768 (ENTRY) OpsConOpen()
TIME:2004/ 4/13-10:35:42:510 TID: 768 (ENTRY) OpsConClose()
TIME:2004/ 4/13-10:35:42:530 TID: 768 (EXIT) OpsConClose(): RetCode=0 Line=562
TIME:2004/ 4/13-10:35:42:530 TID: 768 (ENTRY) OpsConDispose()
TIME:2004/ 4/13-10:35:42:530 TID: 768 (EXIT) OpsConDispose(): RetCode=0 Line=697
TIME:2004/ 4/13-10:35:42:530 TID: 768 (ENTRY) OpsErrGetOraMesg()
TIME:2004/ 4/13-10:35:42:540 TID: 768 (EXIT) OpsErrGetOraMesg(): RetCode=0 Line=298
TIME:2004/ 4/13-10:35:42:870 TID: 788 (ENTRY) OpsSqlFreeValCtx()
TIME:2004/ 4/13-10:35:42:870 TID: 788 (EXIT) OpsSqlFreeValCtx(): RetCode=0 Line=154
TIME:2004/ 4/13-10:35:42:870 TID: 788 (ENTRY) OpsErrFreeCtx()
TIME:2004/ 4/13-10:35:42:870 TID: 788 (EXIT) OpsErrFreeCtx(): RetCode=0 Line=212
TIME:2004/ 4/13-10:35:42:870 TID: 788 (ENTRY) OpsSqlFreeCtx()
TIME:2004/ 4/13-10:35:42:870 TID: 788 (EXIT) OpsSqlFreeCtx(): RetCode=0 Line=105
TIME:2004/ 4/13-10:35:42:870 TID: 788 (ENTRY) OpsPrmFreeValCtx()
TIME:2004/ 4/13-10:35:42:870 TID: 788 (EXIT) OpsPrmFreeValCtx(): RetCode=0 Line=297
TIME:2004/ 4/13-10:35:42:870 TID: 788 (ENTRY) OpsPrmFreeValCtx()
TIME:2004/ 4/13-10:35:42:870 TID: 788 (EXIT) OpsPrmFreeValCtx(): RetCode=0 Line=297
TIME:2004/ 4/13-10:35:42:870 TID: 788 (ENTRY) OpsPrmFreeValCtx()
TIME:2004/ 4/13-10:35:42:870 TID: 788 (EXIT) OpsPrmFreeValCtx(): RetCode=0 Line=297
TIME:2004/ 4/13-10:35:42:870 TID: 788 (ENTRY) OpsPrmFreeValCtx()
TIME:2004/ 4/13-10:35:42:870 TID: 788 (EXIT) OpsPrmFreeValCtx(): RetCode=0 Line=297
TIME:2004/ 4/13-10:35:42:870 TID: 788 (ENTRY) OpsPrmFreeValCtx()
TIME:2004/ 4/13-10:35:42:870 TID: 788 (EXIT) OpsPrmFreeValCtx(): RetCode=0 Line=297
TIME:2004/ 4/13-10:35:42:870 TID: 788 (ENTRY) OpsSqlFreeValCtx()
TIME:2004/ 4/13-10:35:42:870 TID: 788 (EXIT) OpsSqlFreeValCtx(): RetCode=0 Line=154
TIME:2004/ 4/13-10:35:42:870 TID: 788 (ENTRY) OpsErrFreeCtx()
TIME:2004/ 4/13-10:35:42:870 TID: 788 (EXIT) OpsErrFreeCtx(): RetCode=0 Line=212
TIME:2004/ 4/13-10:35:42:870 TID: 788 (ENTRY) OpsPrmFreeValCtx()
TIME:2004/ 4/13-10:35:42:870 TID: 788 (EXIT) OpsPrmFreeValCtx(): RetCode=0 Line=297
TIME:2004/ 4/13-10:35:42:870 TID: 788 (ENTRY) OpsPrmFreeValCtx()
TIME:2004/ 4/13-10:35:42:870 TID: 788 (EXIT) OpsPrmFreeValCtx(): RetCode=0 Line=297
TIME:2004/ 4/13-10:35:42:870 TID: 788 (ENTRY) OpsSqlFreeValCtx()
TIME:2004/ 4/13-10:35:42:870 TID: 788 (EXIT) OpsSqlFreeValCtx(): RetCode=0 Line=154
TIME:2004/ 4/13-10:35:42:870 TID: 788 (ENTRY) OpsErrFreeCtx()
TIME:2004/ 4/13-10:35:42:870 TID: 788 (EXIT) OpsErrFreeCtx(): RetCode=0 Line=212
TIME:2004/ 4/13-10:35:42:870 TID: 788 (ENTRY) OpsPrmFreeValCtx()
TIME:2004/ 4/13-10:35:42:870 TID: 788 (EXIT) OpsPrmFreeValCtx(): RetCode=0 Line=297
TIME:2004/ 4/13-10:35:42:870 TID: 788 (ENTRY) OpsPrmFreeValCtx()
TIME:2004/ 4/13-10:35:42:870 TID: 788 (EXIT) OpsPrmFreeValCtx(): RetCode=0 Line=297
TIME:2004/ 4/13-10:35:42:870 TID: 788 (ENTRY) OpsPrmFreeValCtx()
TIME:2004/ 4/13-10:35:42:870 TID: 788 (EXIT) OpsPrmFreeValCtx(): RetCode=0 Line=297
TIME:2004/ 4/13-10:35:42:870 TID: 788 (ENTRY) OpsSqlFreeValCtx()
TIME:2004/ 4/13-10:35:42:870 TID: 788 (EXIT) OpsSqlFreeValCtx(): RetCode=0 Line=154
TIME:2004/ 4/13-10:35:42:870 TID: 788 (ENTRY) OpsErrFreeCtx()
TIME:2004/ 4/13-10:35:42:870 TID: 788 (EXIT) OpsErrFreeCtx(): RetCode=0 Line=212
TIME:2004/ 4/13-10:35:42:870 TID: 788 (ENTRY) OpsPrmFreeValCtx()
TIME:2004/ 4/13-10:35:42:870 TID: 788 (EXIT) OpsPrmFreeValCtx(): RetCode=0 Line=297
TIME:2004/ 4/13-10:35:42:870 TID: 788 (ENTRY) OpsPrmFreeValCtx()
TIME:2004/ 4/13-10:35:42:870 TID: 788 (EXIT) OpsPrmFreeValCtx(): RetCode=0 Line=297
TIME:2004/ 4/13-10:35:42:870 TID: 788 (ENTRY) OpsPrmFreeValCtx()
TIME:2004/ 4/13-10:35:42:870 TID: 788 (EXIT) OpsPrmFreeValCtx(): RetCode=0 Line=297
TIME:2004/ 4/13-10:35:42:870 TID: 788 (ENTRY) OpsPrmFreeValCtx()
TIME:2004/ 4/13-10:35:42:870 TID: 788 (EXIT) OpsPrmFreeValCtx(): RetCode=0 Line=297
TIME:2004/ 4/13-10:35:42:870 TID: 788 (ENTRY) OpsPrmFreeValCtx()
TIME:2004/ 4/13-10:35:42:870 TID: 788 (EXIT) OpsPrmFreeValCtx(): RetCode=0 Line=297
TIME:2004/ 4/13-10:35:42:870 TID: 788 (ENTRY) OpsSqlFreeValCtx()
TIME:2004/ 4/13-10:35:42:870 TID: 788 (EXIT) OpsSqlFreeValCtx(): RetCode=0 Line=154
TIME:2004/ 4/13-10:35:42:870 TID: 788 (ENTRY) OpsErrFreeCtx()
TIME:2004/ 4/13-10:35:42:870 TID: 788 (EXIT) OpsErrFreeCtx(): RetCode=0 Line=212
TIME:2004/ 4/13-10:35:46:756 TID: 768 (ENTRY) OracleConnection::OracleConnection(2)
TIME:2004/ 4/13-10:35:46:756 TID: 768 (EXIT) OracleConnection::OracleConnection(2)
TIME:2004/ 4/13-10:35:46:756 TID: 768 (ENTRY) OracleConnection::Open()
TIME:2004/ 4/13-10:35:46:756 TID: 768 (ENTRY) OpsConAllocValCtx()
TIME:2004/ 4/13-10:35:46:756 TID: 768 (EXIT) OpsConAllocValCtx(): RetCode=0 Line=129
TIME:2004/ 4/13-10:35:46:756 TID: 768 (ENTRY) OpsConOpen()
TIME:2004/ 4/13-10:35:46:937 TID: 768 (EXIT) OpsConOpen(): RetCode=0 Line=1354
TIME:2004/ 4/13-10:35:46:937 TID: 768 (EXIT) OracleConnection::Open()
TIME:2004/ 4/13-10:35:46:937 TID: 768 (ENTRY) OracleParameter::OracleParameter(4)
TIME:2004/ 4/13-10:35:46:937 TID: 768 (ENTRY) OpsPrmAllocValCtx()
TIME:2004/ 4/13-10:35:46:937 TID: 768 (EXIT) OpsPrmAllocValCtx(): RetCode=0 Line=131
TIME:2004/ 4/13-10:35:46:937 TID: 768 (EXIT) OracleParameter::OracleParameter(4)
TIME:2004/ 4/13-10:35:46:937 TID: 768 (ENTRY) OracleCommand::OracleCommand(1)
TIME:2004/ 4/13-10:35:46:937 TID: 768 (EXIT) OracleCommand::OracleCommand(1)
TIME:2004/ 4/13-10:35:46:937 TID: 768 (ENTRY) OracleCommand::CommandText(): set
TIME:2004/ 4/13-10:35:46:937 TID: 768 (EXIT) OracleCommand::CommandText(): set
TIME:2004/ 4/13-10:35:46:937 TID: 768 (ENTRY) OracleParameterCollection::Add(2)
TIME:2004/ 4/13-10:35:46:937 TID: 768 (EXIT) OracleParameterCollection::Add(2)
TIME:2004/ 4/13-10:35:46:937 TID: 768 (ENTRY) OracleDataAdapter::OracleDataAdapter(2)
TIME:2004/ 4/13-10:35:46:937 TID: 768 (EXIT) OracleDataAdapter::OracleDataAdapter(2)
TIME:2004/ 4/13-10:35:46:937 TID: 768 (ENTRY) OpsPrmResetValCtx()
TIME:2004/ 4/13-10:35:46:937 TID: 768 (EXIT) OpsPrmResetValCtx(): RetCode=0 Line=154
TIME:2004/ 4/13-10:35:46:937 TID: 768 (ENTRY) OpsSqlExecuteReader()
TIME:2004/ 4/13-10:35:46:937 TID: 768 (ENTRY) OpsErrAllocCtx()
TIME:2004/ 4/13-10:35:46:937 TID: 768 (EXIT) OpsErrAllocCtx(): RetCode=0 Line=185
TIME:2004/ 4/13-10:35:46:937 TID: 768 (ENTRY) OpsSqlAllocCtx()
TIME:2004/ 4/13-10:35:46:937 TID: 768 (EXIT) OpsSqlAllocCtx(): RetCode=0 Line=80
TIME:2004/ 4/13-10:35:46:937 TID: 768 OpsSqlExecuteNonQuery(): SQL: SELECT user_id , user_initials , last_name , forename , telephone_no , email_address , initial_profile , user_profile , limited_configurator , intl , plant_access , printing_allowed , reference_text , web_allowed , current_only , approved_only , override_part_val , prod_access , plan_access , phase_access , view_bom FROM application_user WHERE application_user.USER_ID = :userid

I need db block corruption query

Hi all,
In my database some of the blocks are corrupted.
seelect * from v$database_block_corruption;
31 rows selected.
i need to find which object_name,owner,blocks,file_id are corrupted details.
please send the query.
Regards
Rajabaskar

RajaBaskar Thangaraj wrote:
i need to find which object_name,owner,blocks,file_id are corrupted details.
please send the query.
Use the dbverify tool to give you the block corruption ,owner,block etc
$ dbv file=/u01/app/oracle/oradata/testdb/users01.dbf blocksize=8192
Hope that helps
http://www.dba-oracle.com/tips_oracle_dbv_verify.htm

Corrupted query statement in MySQL

Occasionaly queries are truncated resulting in an error. The
problem is not repeatable, the same query runs fine for a long time
and then suddenly it gets truncated. It doesnt appear with a
specific query but randomly.
An example:
SELECT * from tablename
Is run like
LECT * from tablename
Truncation appears at the start of the string as well as at
the end.
We are using MX7.0.1 (multi-server cluster, enterprise
edition) with a MySQL 4.0.2 database (MysQL 3.x connector).
Analysis of the logs shows that we first had this problem
when we moved from the Professional to the Enterprise Edition, and
the problem only occurs when there is a heavy load on the
machines.

Hi,
I assume you have already written a query to get the lecturers,
What you need to do is, create a parameter of type string, right click to edit it. Click on Defualt Values, you will get a window Set Default values, Select the command/table from the first drop down, select the field in your case lecturer from the second drop down, When you do that all the values will be listed on the left side, Select all of them and push into the right list by clicking the > sign. Click Ok and uncheck the Allowe editing the defualt values check box and click Ok, please note that the values will have to be reset if there is a change in the db query.
Hope this helps,
Thanks
-Azhar

Corrupted Query Designer with strange External Restriction

Dear Experts,
I have a dilemma with query, when I run the query in RSRT and debug it with OLAP, in the restriction side it appears to restrict the query with two Attributes which are not even used in my query not also their master-data.
I have created the same query again but still it gave the same behavior.
Please help me to remove this dilemma.
Regards,
Mohammed

close all applications re-use RSRT
hope it works

How to find the corrupted files using javascript?

Hi all,
I need to run batch of files some of which were corrupted?? instead of using the method "the files which were not opened are corrupted" is there any way to find the corrupted files??
I need to find this using javascript or apple script??
Please some one help me..
Regards,
subha

We found one datafile has corrupted by using dbv.dbv would have reported the block ids (block numbers) that are corrupted.
query dba_extents to identify the segments that contain such blocks.

Launch of new NW2004s-BI Frontend from transaction rrmx

Hi,
my customer has upggraded to NW2004s. We are on Support Package 7. The NW2004s-BI Frontend is FEP701.
When I enter transaction <rrmx> the "old" BW 3.5 Bex Frontend launches.
Is there a way to have <rrmx> call the new NW2004s-BI frontend?
I have been toggling the "Launch Legacy Version from RRMX" flag on and off in the new NW2004s BI Frontend but nothing but the 3.5 Analyzer lauches?
Can you help with that issue?
Thanks
Christian

Hi Christian! in this reply you could find your solution.
 but attached file is available only by OSS!
If you think this helps, don't forget give me points!
see note 933768
Symptom
Error in Business Explorer Components like Analyzer, Report Designer, Web Application Designer, Query Designer, Open/Save Dialog, Value Help Dialog
Other terms
Business Explorer, Frontend, BW, BI 7.0, BI, Hotfix, advance correction, Analyzer, Report Designer, Web Application Designer, Query Designer, Open/Save Dialog, Value Help Dialog, Selector, characteristic restriction, filter, filter value, variables
Reason and Prerequisites
You have installed NetWeaver 2004s BI Add-On Frontend Patch 700, and you need a hotfix (advance correction) for certain problems that are caused by the BI Add-On (frontend).
This note will be updated as solutions for newly detected problems are available. Hence you should check the actuality of this note, if you have already applied hotfixes for the patch level of your BI Add-On.
Solution
Attached to this note you will find frontend components (DLL files) that correct certain errors. You will find a list and descriptions of solved problems in the following. It is recommended to replace all respective DLLs in the setup directory of the BI Add-On with the attached DLLs. However, you can also selectively replace individual DLLs that are required for the solution of problems that you encountered. In the following it is described which DLLs are required to solve specific problems.
The Open/Save dialog and the Value Help dialog (selector) are components that are used by several SAP Business Explorer applications. Hence, if you encounter errors in one of those applications, please also check the dialogs sections below for a solution.
SAP Business Explorer Web Application Designer
SAP Business Explorer Analyzer and Variables Screen
New property to adjust the size of the Drop-down item added.
Known errors occuring, while entering the values in variable screen pop-up, have been corrected
SAP Business Explorer Query Designer
Corrected critical error at saving of reusable elements (especially evident with calculated key figures using variables). We strongly recommend to apply this hotfix.
If a presentation hierarchy is selected for a drilldown, it is not possible any more to restrict the characteristic to a hierarchy node from another hierarchy.
Refresh problem solved with repeated query execution in web browser.
Dimension preview is enabled again and allows scrolling.
Problems with query variable order presentation and editing are solved.
Structure member selections using calculated key figures display further calcuated key figure properties.
Error with characteristic value variables replaced by queries corrected.
Errors with structure member descriptions corrected.
There were too many characteristics offered as aggregation reference for formulas. Now only characteristics of the corresponding InfoProvider are listed.
Paste of multiple characteristics when restricting structure member selections is working again.
Error when creating structure member hierarchies with formulas is solved.
Copy and paste of a structure member without changing the focus was not possible. This is now enabled.
Variables could not be entered in the editors for conditions and exceptions. This is possible now. Also variables for key date can now be entered.
Error when adding attributes by drag and drop corrected.
Sorted display of query elements corrected.
Paste of a second reusable structure enabled again.
It is not allowed to restrict a structure member to a characteristic value if the other structure already contains a restriction of this characteristic. This check is now implemented.
Sometimes values for Zero Suppression were not correctly saved. This is corrected now (updated 04 May 2006)
Restricted and Calculated key figure folders did not display if the user started Query Designer more than once from Analyzer. (updated 04 May 2006)
It was not possible to delete a Characteristic from filter if a reusable filter contained this characteristic (updated 04 May 2006)
Paste of InfoObjects and reusable Elements was errorneously possible to Exception and Condition area. Is frobidden now. (updated 04 May 2006)
Text variables with repalcement path are now always not inputable (updated 04 May 2006)
Variables were not displayed correctly if the user started Query Designer more than once from Analyzer. (updated 04 May 2006)
There could be a runtime error (occasionally) in Anaylzer after user selected "Exit and use query" in Query Designer due to a still processed error check. (updated 04 May 2006)
There is now a check if a presentation hierarchy exists on server. If not, the user is informed by a warning (updated 04 May 2006)
New warning informs user about non existing presentation hierarchies (updated 15 May 2006)
Formula variables with replacement path "by attribute" offer now only numerical attributes. (updated 15 May 2006)
Empty formulas now cause an error message, not just a warning message, because queries with empty formulas are not executable. (updated 15 May 2006)
For compounded characteristics in InfoProvider tree the compound info was not displayed in all cases, this is corrected now (updated 15 May 2006)
Variables replaced by query result or by a replacement table can be just used in Filter. The user is informed by an error message if such variables are used anywhere else (updated 15 May 2006).
Queries with cell were sometimes saved with wrong coordinates for cells. Such queries are not executable. This is corrected now. Wrong queries are auto corrected, if they are loaded and saved with this corrected version (updated 15 May 2006).
Problem with "hanging" explorer during execution of a query in web solved (updated 15 May 2006).
Variable order setting is now also possible for new queries (updated 15 May 2006)
Empty structures cause now an error message, not just a warning message, because queries with empty structures are not executable. (updated 15 May 2006)
There were some cases where Text variables were not stred correctly and as a consequence not replaced. All known issues are now corrected. (updated 15 May 2006)
With this hotfix the Note 948374 should be also implemented in the backend system, it prevents some save prolems.
Small usability improvements in Varible-, Exception- and Condition editor (updated 23 May 2006)
Multiple keyfigures are not allowed in Filter, but it was possible to do this with copy and paste of multiselected keyfigures (updated 23 May 2006)
There were cases where users could create different components with same technical names, this is checked now (updated 23 May 2006)
Variables replaced by query result or by a replacement table reported an incorrect message if they were defined with "Input allowed = true", this is corrected (updated 23 May 2006)
SAP Exit variables were errorneously not allowed to be used in non content systems, this is corrected (updated 23 May 2006)
In variable editor for Formula variables replaced by attribute value there were not offered all possible numeric variables offered. This caused a runtime error if especially variables created with Query Designer 3.x were edited. This is corrected now (updated 23 May 2006)
Due to a program error any saved formula might have been saved incorrectly, if it is using any variables (formula or text variables). This is a critical error which might lead to not understandable error messages during query execution or missing text variable replacement for formulas. The error is corrected the was that any corrupt query can be loaded and after a save it is repaired. We strongly recommend to use this hotfix for all installations!
SAP Business Explorer Report Designer
Introduced Versioning and added Version checks. More recent versions of Report Designer are able to design reports with new features. If such a report is edited with an older version of Report Designer some design features might be lost in the report or loading the report might not be possible.
Images from Mime repository can be added to the report.
Sequence of Report Sections is saved and loaded in the right order.
Query Text Elements for more than one Dataprovider are correctly dsiplayed in the Report Item. Property Dialog shows the name of the Dataprovider of the selected Text Element.
Conditional Formatting for Hierarchy nodes enabled.
Open Dialog/Save Dialog
Value Help Dialog (Characteristics Restriction/Filter Selection)
Search can be performed by entering the search criteria in value help dialog and then by pressing the <Enter> keyboard button
or see note 929632
Symptom
There are errors in Business Explorer components such as Analyzer, Report Designer, Web Application Designer, BEx Query Designer, Open/Save dialog, input help dialog.
Other terms
Business Explorer, Front end, BW, BI 7.0, BI, Hotfix, advance correction, Analyzer, Report Designer, Web Application Designer, BEx Query Designer, Open/Save dialog, input help dialog, selector, characteristic restriction, filter value, variables
Reason and Prerequisites
You have installed NetWeaver 2004s BI Add-On Front End Patch 02 and you require advance corrections for certain problems that are caused by the BI Add-On (front end).
Solution
You can find front end components (DLLs) that correct the errors described below attached to this note. We recommend that you replace all attached DLLs in the setup directory of the BI Add-On. However, you can also replace only those DLLs required to correct a problem that occurred in your system. The following sections describe which DLLs correct which problems.
The Open/Save dialog and the input help dialog are components that are used by several SAP Business Explorer applications. Therefore, check whether the correction of a problem that occurred in one of the applications is described there.
SAP Business Explorer Web Application Designer
 Up to now, there are no advance corrections.
SAP Business Explorer Analyzer and variable screen
 To correct the problems in the Analyzer and the variable screenthat are described here, the files BExApi.dll, BExAddin.dll, BExAnalyzer.xla, BExVariableScreen.dll, BExLocalFormulaParser.dll, BExQueryDesigner.dll, BExSelectorAPI.dll and BExSelectorDialog.dll are required.
In the variable screen, the formats for the calendar year and calendar month characteristics have not been transferred correctly to the server. As a result, error messages occurred during the check.
When deleting an item in design mode, the system did not remove the displayed data of the item in analysis mode, rather it still displayed this data.
The display of the checkbox item and the radio button item has been corrected.
Errors occurred when you saved variants on the variable screen. All known errors have been corrected.
The security certificate for the Analyzer has expired and the advance corrections contain a new security certificate.
SAP Business Explorer Query Designer
 To correct the problems in the Query Designer that are described here, the files BExQueryDesigner.dll, BExSelectorAPI.dll and BExSelectorDialog.dll are required.
Executing in the Web no longer opens different browser windows, rather the system always uses the same one.
In certain cases, queries that contain attributes were not saved correctly and as a result, they could not be loaded. This problem has been corrected in all known the cases.
In certain cases, queries that contain cells were not saved correctly and as a result, they could not be loaded. This problem has been corrected in all known the cases.
If queries are saved incorrectly (for example with incorrect attributes or incorrect cells), the system issues messages for all cells that are incorrect and it refers to a possible solution. Currently, all text messages are in English and they will be translated in Support Package Stack 8.
You can now insert and resort attributes at any position. You can do this using drag and drop or cut and paste.
Formula variables with replacement path now also permit the setting of the dimension.
If you edited attributes for an object and you then saved your changes immediately without exiting the field, the system did not save the change in this field. This problem has now been corrected.
Texts of attributes are now displayed correctly after you load the query again (up to now, the system displayed only technical names).
Constant selection was not displayed correctly in the context menu of a selection. Now, the system displays a checkmark to indicate that constant selection is activated.
Attributes of display hierarchies are now displayed and saved correctly.
The system no longer displays operators twice in technical names in formulas. Up to now, [+] + was displayed.
The system no longer displays UIDs as technical names for structure items and cells in formulas.
Structures with hierarchical structure items: In certain cases, structure elements disappeared during the hierarchical setup. However, these were saved and they caused an endless loop on the server. This problem has been corrected. You can use the BEx Query Designer to open queries that were saved with these "vanished" structure elements and the "vanished" structure elements are displayed again.
Errors and terminations on the server now cause a message in the message window of the BEx Query Designer telling you to close and to restart the BEx Query Designer.
For variables with replacement path, the system displayed too many characteristics (some technical characteristics) for the replacement characteristic. This problem has been corrected.
Further consistency checks have been implemented and the corresponding messages are displayed in the message list. The system now checks not only queries but it also checks restricted and calculated key figures, variables, and cells.
If you change a reusable element, the system does not save it automatically. An information message is displayed telling the user that saving the element may affect other queries. You can save the element normally using a save function in the context menu. If the element is used in the query, it is always saved with the query.
When you exit the BEx Query Designer, the system checks which reusable elements have not yet been saved. The system displays a list containing all unsaved elements and it asks the user whether these elements should be saved.
There is a new menu function "Save All" that saves all changed reusable elements.
When you select text variables, the system now displays the correct variable type "Text variable" in the selection.
You were able to use cut and paste for conditions and exceptions, but this always caused a runtime error. The functions have been deactivated for the moment to avoid program terminations.
You can now define variables with a replacement from an attribute.
You can now also display only posted values in the value help (read mode D).
For text and formula variables with replacement path, you can no longer create on the technical characteristic 1TEXT or 1FORMULA. Any existing variables (that were created with earlier versions) are reported as incorrect and you should delete them.
For restricted or calculated key figures or for variables, if you made changes and you saved these changes online and confirmed with OK, the system sometimes issued message "Not saved - object is not changeable". This problem has been corrected.
When creating new reusable elements, the system only checked if the user was authorized to create new elements for this InfoProvider, but it did not check whether the user was authorized to create elements with the given technical name. This problem has been corrected.
You can now move and copy cells using cut and paste and copy and paste. Unfortunately, you still cannot use drag and drop.
In formulas, multiline headers of structure elements are correctly displayed in single lines and no longer in several lines.
In certain cases, hierarchy node variables were saved without a corresponding hierarchy assignment and you could not use them in the report that was being executed.
After each time you saved data, the context menu of the currently selected object was incorrect. This problem has been corrected.
You could not delete filter values directly in the BEx Query Designer, rather you had to do this in the filter dialog.
You could not change characteristics of attributes.
The system now issues a corresponding success message after each successful saving process.
SAP Business ExplorerReport Designer
 Up to now, there are no advance corrections.
Open dialog/Save dialog
 Up to now, there are no advance corrections.
Input help dialog (characteristic value restriction/filter selection)
 To correct the problems in the value help dialog that are described here, the files BExQueryDesigner.dll, BExSelectorAPI.dll and BExSelectorDialog.dll are required.
You can now edit variables in the value help for all variable types and not only for characteristic value variables.
You can now create variables in the value help for all variable types and not only for characteristic value variables.
When changing an offset, negative offsets are displayed as -5 and no longer as 5-. Variable offsets are displayed directly in the right area of the value help.
Variables as the to-value of intervals no longer cause terminations.
In the value range editor, the value you entered manually was not transferred if you directly chose the transfer arrow.
In the value help for reference characteristics, the system did not display the variables for basic characteristics and therefore there were usually fewer variables than in the BEx Query Designer.
When you select the hierarchy, the system now correctly displays the date and version variables and no longer hierarchy variables as was incorrectly the case before.
When you call the value help from the variable entry screen, the system sometimes displayed all master data values (read mode "M") even though it should only display posted values (read mode "D"). This problem has been corrected.

Calculated Key Figures Corrupted in a BEX Query

Hello SDN's,
We are facing an weird issue in BEX Query. As part of Enhancing the query, We have created a new CKF and added in the Columns for the required CKF. It prompted for a Transport request and saved the Query elements for more than hour. Now the Query is throwing an Error messages where in more than some 30 CKF's got corrupted. When i check the CKF definition for all the corrupted key figures there is not Formula or Calculation.
Below is the message which we can see in the BEX query for Corrupted Calculate Key Figure.
Diagnosis
Element ' XXX ' cannot be analyzed by the analytic engine without a definition.
System Response
Without a valid definition, the element will be ignored by the analytic engine.
Procedure
Provide a valid definition for element 'XXX'.
Could anyone please help me to retrieve query back to normal ???. Your are inputs are appreciated
Thanks,
HA

yo could try rsrt in bw and try to regenrate the query thats all i got. .otherwise always make a copy before you start working on a query. if it still is coruupted then you will have to recrate it. if the query is in your bwq maybe the basis can do a transport( not recomended)back. good luck..

SQL query to correct the corrupted data

Hi All,
I got strucked up with a query correcting the corrupted records.
CREATE TABLE EX1
EMPID INTEGER,
DW_EFF_DT DATE,
DW_EXPR_DT DATE
INSERT INTO EX1 VALUES(1,'04-MAR-1998','13-MAR-1999');
INSERT INTO EX1 VALUES(1,'14-MAR-1999','02-MAY-2000');
INSERT INTO EX1 VALUES(1,'03-MAY-2000','01-MAY-2013');
INSERT INTO EX1 VALUES(1,'02-MAY-2013','31-DEC-9999');
I have empid with other attributes,we are maintaing history.There is some data which is corrupted and we need to correct it.
DW_EFF_DT which is less than '01-FEB-2005' should be made by default '31-JAN-2005'
Again the data should be corrected and my output should be like the below
EMPNO DW_EFF_DT DW_EXPR_DT
1 2005-01-27 2005-01-28
1 2005-01-29 2005-01-30
1 2005-01-31 2013-05-01
1 2013-05-02 9999-12-31
I used the lead and lag function,but it is applied sequentially.
How I can get the dates subtratcing by 1 for each and every alternative row.
I tried the below query and able to achive half of it.
SELECT A.* ,COALESCE(LEAD(NEW_DW_EFF,1) OVER(ORDER BY NEW_DW_EFF) -1,TO_DATE('31-DEC-9999','DD-MON-YYYY')) AS NEW_DW_EXPR_DT
FROM
SELECT ID,
DW_EFF_DT,
DW_EXPR_DT,
CASE WHEN DW_EFF_DT<TO_DATE('01-FEB-2005','DD-MON-YYYY') THEN TO_DATE('31-JAN-2005','DD-MON-YYYY') ELSE DW_EFF_DT END AS NEW_DW_EFF
FROM EX1
)A
ID DW_EFF_DT DW_EXPR_DT NEW_DW_EFF NEW_DW_EXPR_DT
1 04-MAR-98 13-MAR-99 31-JAN-05 30-JAN-05
1 14-MAR-99 02-MAY-00 31-JAN-05 30-JAN-05
1 03-MAY-00 01-MAY-13 31-JAN-05 01-MAY-13
1 02-MAY-13 31-DEC-99 02-MAY-13 31-DEC-99
Please help me in this regard.i am still trying it.
Thanks in advance,
KVB

KVB wrote:
EMPNO DW_EFF_DT DW_EXPR_DT
1 2005-01-27 2005-01-28
1 2005-01-29 2005-01-30
1 2005-01-31 2013-05-01
1 2013-05-02 9999-12-31
Actually the last record is the active record.
Th 3rd record effectiuve date is adjusted because the dateis less than 2005-02-01. So that we adjusted to 2005-01-31,
The 2nd record expiry date will be adjusted to 3rd record effective date-1,
Now the 2nd record effective will be adjusted to 2nd record expiry date-1 and so on..until the first record.
Actually I could not explain much better in business point of view like why they do this.Technically we need to achive this through SQL.
CheersOkay, that makes more sense, thanks :)
Probably not the prettiest ... but should work (you may need to tweak it a bit)
ME_TUBBZ? select
2 empid
3 , to_date('2005-02-01','yyyy-mm-dd') - ( 2* rn) + 1 as new_eff_date
4 , case
5 when rn = 1
6 then
7 dw_expr_dt
8 else
9 to_date('2005-02-01','yyyy-mm-dd') - (2 * (rn - 1))
10 end
11 as new_exp_date
12 , dw_eff_dt
13 , dw_expr_dt
14 from
15 (
16 select
17 empid
18 , dw_eff_dt
19 , dw_expr_dt
20 , row_number() over (partition by empid order by dw_eff_dt desc) as rn
21 from ex1
22 where dw_eff_dt < to_date('2005-02-01','yyyy-mm-dd')
23 )
24 order by dw_eff_dt asc
25 /
 EMPID NEW_EFF_DATE NEW_EXP_DATE DW_EFF_DT DW_EXPR_DT
 1 27-JAN-2005 00 00:00 28-JAN-2005 00 00:00 04-MAR-1998 00 00:00 13-MAR-1999 00 00:00
 1 29-JAN-2005 00 00:00 30-JAN-2005 00 00:00 14-MAR-1999 00 00:00 02-MAY-2000 00 00:00
 1 31-JAN-2005 00 00:00 01-MAY-2013 00 00:00 03-MAY-2000 00 00:00 01-MAY-2013 00 00:00
3 rows selected.
Elapsed: 00:00:00.01
ME_TUBBZ? Cheers,

Sql developer query window corrupting on scroll

Hi there
I have a weird error - when I scroll in my SQL developer query window (tab) the text corrupts and only comes back if I click in the window somewhere or save. Has anyone else seen this? I'm on version 1.5.5 and don't really want to upgrade to the latest as I don't like the new layout (no dbmsoutput etc in the results window)
Cheers, Kate

sorted it by adding a line AddVMOption -Dsun.java2d.noddraw=true to the sqldeveloper.conf file, as per thread SQL Editor not refreshing after scroll on Windows Vista

Bex Analyzer Query Corrupted

Hi All
I have a query in Production Server which got corrupted by a wrong formula and saved subsequently and it doesn't open anymore.
I can delete it by RSZDELETE. However there is a good version of the same query in the Development Server. How to give a Transport Request to this Query and transport it to the Production Server...Please give your idea on this.
Thanks and best regards
Subin

Hi,
Goto the query designer and do some small change(like adding a field) and save the query. It will ask for transport request. Save the query in the transport request. Then undo the changes and then save the query and transport the query. You can also collect the query in transport connection and transport.
Regards,
Raghavendra.

Corruption Parameters Increase High Physical Read for one query

Hi Oracle Experts,
Here is what I am currently facing in my non-prod environment:
We are testing out corruption parameters in non-prod environment and doing a perf test for them and we found that one SELECT query has seen significant decreases in performance; What I mean by that is after adding corruption parameters query is executing 40 sec compare to 18 sec and less. Also, this query is widely use by user in Prod environment, so performance degradation will create serious impact on their work.
I have generated AWR Diff for baseline and perf test following are parameter we have set for corruption test:
db_block_checking (Baseline) LOW (Perftest) MEDIUM
db_block_checksum (Baseline) TRUE (Perftest) FULL
Load Profile from AWR Diff are below:
Load Profile
1st Per Sec 2nd Per Sec %Diff 1st Per Txn 2nd Per Txn %Diff
Redo size: 758,356.06 752,760.94 -0.74 67,161.76 66,631.71 -0.79
Logical reads: 104,637.62 108,677.76 3.86 9,266.95 9,619.77 3.81
Block changes: 1,578.11 1,560.15 -1.14 139.76 139.76 0.00
Physical reads: 103.78 544.41 424.58 9.19 48.19 424.37
Physical writes: 108.94 107.13 -1.66 9.65 9.48 -1.76
User calls: 3,477.02 3,497.26 0.58 307.93 309.57 0.53
Parses: 948.36 949.61 0.13 83.99 84.06 0.08
Hard parses: 0.79 0.54 -31.65 0.07 0.05 -28.57
Sorts: 121.48 120.32 -0.95 10.76 10.65 -1.02
Logons: 0.36 0.27 -25.00 0.03 0.02 -33.33
Executes: 1,575.55 1,591.40 1.01 139.53 140.87 0.96
Transactions: 11.29 11.30 0.09
If we gather stats for tables involved in the query than it performs well in fact with in 5 Sec, but I believe in prod we can't gather state very often.
Questions:
1) How to remedy this situation and have query perform well along with corruption parameters?
2) Does corruption parameters have impact on SELECT query too, I believe it will have impact on INSERT and UPDATE.
3) Any reference to Doc will be highly appreciated.

1) How to remedy this situation and have query perform well along with corruption parameters?Use faster CPU. Checksum is a thing that needs to be computed.
2) Does corruption parameters have impact on SELECT query too, I believe it will have impact on INSERT and UPDATE.According to docs corruption parameters do not have impact on SELECT queries.
However, I believe, checksum has to be recomputed after delayed block cleanout that may be done by SELECT query after big update. ( http://jonathanlewis.wordpress.com/2009/06/16/clean-it-up/ )
3) Any reference to Doc will be highly appreciated.
Why is it difficult for you to find the docs yourself?

Database version 2.3.10 Corruption after query during insert.

I am using DBXML Version 2.3.10. We recently discovered a problem when querying DBXML while inserting (concurrent). Below are the events that occur. I am in the process of getting more details, but I wanted post this in an effort to see what areas I need to concentrate on.
1. Begin inserting XML docs into DBXML. This process also used our unique ID to add a row into Berkeley DB. The insert rate is quite fast. We are real happy with this. We don't see any problems before we query.
2. We submit a query in another thread, as insertion continues. Some time after, we get an exception (FILE_NOTFOUND). However, insertion still seems to be ok, as well as query.
3. At some point thereafter when we run another query, we will encounter an uncaught C++ exception:
Uncaught exception from C++ API
com.sleepycat.dbxml.XmlException: Uncaught exception from C++ API, errcode = INTERNAL_ERROR at com.sleepycat.dbxml.dbxml_javaJNI.XmlContainer.putDocument__SWIG_2(Native Method) at com.sleepycat.dbxml.XmlContainer.putDocument XmlContainer.java:373)
From this point forward, insert fails as well as query. If I try to run a lookupindex()query the database in DBXML Shell, I get DB_PAGE_NOT_FOUND exception. The database is essentially corrupt. This data was collected at a test excercise, and I am desperately trying to recover the data.
If I back off to version 2.2.13, there are no problems. From some other threads of the forum, I noted increasing cache and locks might be helpful. Here are the current settings from the DB_CONFIG file:
set_cachesize 0 250000000 1
set_lk_max_lockers 100000
set_lk_max_locks 100000
set_lk_max_objects 100000
If anyone can offer any other suggestion, we would greatly appreciate it. Version 2.3.10 offers query interrupt/timeout, as well as excellent insert and query performance. We really cannot afford to back off to 2.2.13.
Anthony

Hi Anthony,
I get execeptions such as "configured environment flags incompatible with >existing environment"The error message above suggests an old environment existed prior to your creating the new one (for the Concurrent Data Store). You may want to remove/rename your config flags and just start out with the minimum flags to configure CDS. If there are old environment files delete/remove them (__db.00#).
EnvironmentConfig ec = new EnvironmentConfig
ec.setInitializeCDB(true);
ec.setAllowCreate(true);
ec.setInitializeCache(true);
You don't want to set flags that deal with transactions or the transactional lock system. Therefore do not call setInitializeLocking for example.
For Berkeley DB XML, it is recommeded that you turn on the lockAllDatabases flag:
http://www.oracle.com/technology/documentation/berkeley-db/db/java/com/sleepycat/db/EnvironmentConfig.html#setCDBLockAllDatabases(boolean)
For more information about the Concurrent Data Store:
http://www.oracle.com/technology/documentation/berkeley-db/db/ref/cam/intro.html
Ron Cohen
null

Office 365 Excel Power Query Preview Problem Signing In -- Appears Corrupted, Please Repair

The image below shows that Excel "thinks" I'm signed in with an organizational account that has Power BI Preview, yet Power Query from Excel doesn't think I'm signed in and says it's corrupted when I try to sign in. I was trying to use the
online search to find the odata feed that I have set up for Office 365 Power BI Preview. So, alternatively, when I go to other data sources and specify the odata feed that is set up properly and available, Microsoft says "access forbidden".
Clearly, account credentials aren't being passed correctly. I have read other posts on this forum and have verified that I have the latest Power Query Preview, that I only use lower case letters to sign in, that IE cache is clear. I have repaired,
uninstalled and re-installed Power Query Preview multiple times, with no change in this behavior.
Any ideas?
Neil

Zarar, yes, tried that, and much more.
Even though Power BI is supposed to navigate through firewalls, I believe we are having firewall problems.
I need to ask our network people to open up for Microsoft on this one, but there's no good information out there on the sites/IPs required to make Power BI Preview work.
In addition, the complexity that comes with using domain credentials, Microsoft Account (live) credentials, and Organizational credentials (O365) on the same computer at various times of the day complicates matters.
That said, I can take my machine to my home network and get as far as attempting to connect to the odata feed I set up -- except the data source is on a computer with an internal IP and Power Query cannot resolve the local computer name -- i.e. x.x.local.
So now, I have two questions:
1. What IPs need to be unblocked to make Power BI work?
2. Is there a way to get the odata feed to work when the datasource is on an internal network (the datasource is working and tests okay from Power BI Admin -- but does not resolve the machine name when coming in through Excel via the odata feed from an off-site
location
Neil

Corrupted structures within query's

Any help appreciated.
I have a structure within a query which seems to have become corrupted in some way and therefore no longer works. When the structure is re-created in exactly the same way however it works fine. The structure is used in several query's and I do not want to have to re-create it again in each of them. Is there any way I can find out why a structure has become corrupted?, or fix it in a way which will refresh all the related query's?
For info; the BW system has recently been upgraded from BW3.1 to BI7.
Many Thanks

Lee,
try reimporting your structure from DEV.... it could be possible that it has got corrupted due to some changes not being done properly.
Am not too sure if you can do a where used list for the same.... try using the where used list in the query designer but usually it is local to the query
Arun

Corrupted Query

Similar Messages

Maybe you are looking for