4.0EA3 Bug - UK Column Not Applied on Entity

When I create a unique identifier (UID) before creating the UID attribute, then create the UID attribute, re-open the UID and move the new UID attribute into the UID, click OK or APPLY in UK constraint dialog and OK or APPLY in the entity dialog, I get the error message "Incomplete Unique Identifier definition". I go back into the UID and the UID attribute has moved back out. Solution is to delete the UK Constraint, click APPLY then create the UID attribute.

I've forgot to mention, that my default RDBMS Site is set to SQL Server 2008. In Types Administration UNIQUEIDENTIFIER is mapped to CHAR for Oracle, but it mapped to UNIQUEIDENTIFIER for SQL Server 2008.

Similar Messages

SQL Server 2008 R2 Replication - not applying snapshot and not updating all repliacted columns

We are using transactional replicating on SQL Server 2008 R2 (SP1) using a remote distributor. We are replicating from BaanLN, which is an ERP application to up to 5 subscribers, all using push publications.
Tables can range from a couple million rows to 12 million rows and 100's of GBs in size.
And it's due to the size of the tables that it was designed with a one publisher to one table architecture.
Until recently it has been working very smooth (last four years)) but we have come across two issues I have never encountered.
While this has happen a half dozen times before, it last occurred a couple weeks ago when I was adding three new publications, again a one table per publication architecture.
We use standard SS repl proc calls to create the publications, which have been successful for years.
On this occasion replication created the three publications, assigned the subscribers and even generated the new snapshot for all three new publications.
However, while it appeared that replication had created all the publications correctly from end to end, it actually only applied one of the three snapshot and created the new table on both of the new subscribers (two on each of the
publications). It only applied the snapshot to one of the two subscribers for the second publications, and did not apply to any on the third.
I let it run for three hours to see if it was a back log issue.
Replication was showing commands coming across when looking at the sync verification at the publisher and
it would even successfully pass a tracer token through each of the three new publications, despite there not being tables on either subscriber on one of the publishers and missing on one of the subscribers on another.
I ended up attempting to reinitialize roughly a dozen times, spanning a day, and one of the two remaining publications was correctly reinitialized and the snapshot applied, but the second of the two (failed) again had the same mysterious result, and
again looked like it was successful based on all the monitoring.
So I kept reinitializing the last and after multiple attempts spanning a day, it too finally was built correctly.
Now the story only get a little stranger. We just found out yesterday that on Friday the 17th
at 7:45, the approximate time started the aforementioned deployment of the three new publications,
we also had three transaction from a stable and vetted publication send over all changes except for a single status column.
This publication has 12 million rows and is very active, with thousands of changes daily.
, The three rows did not replicate a status change from a 5 to a 6.
We verified that the status was in fact 6 on the publisher, and
5 on both subscribers, yet no messages or errors. All the other rows successfully updated.
We fixed it by updating the publication from 6 back to 5 then back to 6 again on those specific rows and it worked.
The CPU is low and overall latency is minimal on the distributor.
From all accounts the replication is stable and smooth, but very busy.
The issues above have only recently started. I am not sure where to look for a problem, and to that end, a solution.

I suspect the problem with the new publication/subscriptions not initializing may have been a result of timeouts but it is hard to say for sure. The fact that it eventually succeeded after multiple attempts leads me to believe this. If this happens
again, enable verbose agent logging for the Distribution Agent to see if you are getting query timeouts. Add the parameters
-OutputVerboseLevel 2 -Output C:\TEMP\DistributionAgent.log to the Distribution Agent Run Agent job step, rerun the agent, and collect the log.
If you are getting query timeouts, try increasing the Distribution Agent -QueryTimeOut parameter. The default is 1800 seconds. Try bumping this up to 3600 seconds.
Regarding the three transactions not replicating, inspect MSrepl_errors in the distribution database for the time these transactions occurred and see if any errors occurred.
Brandon Williams (blog |
linkedin)

Formatting Critical Tasks (Text in Table) not applying across all columns

All,
I am working on creating a schedule from multiple smaller schedules. A few of these schedules had manual text formatting which I overwrote manually (selecting cells and changing text color). Now when attempting to apply text styles to the critical
path the text styles will not apply to all Critical tasks or all columns visible. I'm guessing I caused problems by manually changing the text color but I don't know how to fix it. Please help!

All of the manual text formatting and re-formatting in cells has changed the default formatting in the Gantt Chart View.
Rather than fiddling with it, the best way is to recover the original formatting of the Gantt Chart View, and then if you want to modify it make a copy of that view, name the copy something like "AA Gantt Chart 01", and then format the text and bar
styles (not individual bits and pieces of cells and bars) of your new view. Include the "AA" or an underscore or something similar as part of the name so that your new views always go to the top of the list and you can always distinguish them
from the original ones that came out of the box.
Use the organiser to recover the original Gantt Chart View by pulling the Gantt Chart View from the global template. Now, MSP will not allow you to over-write the Gantt Chart View in your file while that view is the active view, so you will have to switch
to another view while you do it. Switch to the Tracking Gantt View, then File, Organiser. You see all of the clean stuff on the left hand side and all of the stuff in your file on the right.
In the future, leave the original views as they are. Also, leave the original tables, filters, groups, reports etc alone and if you need modified/customised versions of them make copies and change the copies. This is just good housekeeping. Also, do not
copy modified/customised views from your file into the global template ((or you will poison the well).
Hope this helps. Please mark as answer.

Changed column order not applied to interactive report

Hi,
I've changed column order for interactive report.
But it is not applied.
How can I solve this issue?
Thanks,
Guy

Hi Guy
It depends on where you have changed the column order. If you change the column order using the 'Select Columns' function when you click on the 'Wheel of Magic', then it should work.
If you are changing the column order from the Interactive Reports Attributes page then this will only affect the column order for non displayed items and the single row view.
I hope that helps
Shunt

BUG: "circle" column in message list not resize-able

I've noticed a very annoying bug- the column which contains the blue dot for unread messages, and also the message count for the line if "View - Organize by Thread" is turned on, cannot be resized. This means that if a particular line is a collapsed thread, you can't see how many messages are in that thread.
I took a screen shot of what I'm talking about, if the description above isn't clear.

This was apparently fixed with the 10.5.0 to 10.5.1 OS upgrade. Thanks, Apple, for acknowledging the problem or letting me (or anybody) know it was being fixed...

Log is not applied, subsequent log applied are "yes"

Hi all,
I am building a new standby.
It is brand new, and I have turned on the managed recovery for the first time after restoring my database.
--> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
Why does the first line show "NO" for applied log? (and all the logs after it shows "YES"?)
Is there something wrong, or can I ignore this as it is normal?
SQL> SELECT sequence#, first_time, next_time, applied
FROM v$archived_log
ORDER BY sequence#; 2 3
SEQUENCE# FIRST_TIME NEXT_TIME APP
2653893 30-OCT-2012 23:03:21 30-OCT-2012 23:03:25 NO
2653894 30-OCT-2012 23:03:25 30-OCT-2012 23:23:04 YES
2653895 30-OCT-2012 23:23:04 30-OCT-2012 23:23:28 YES
2653896 30-OCT-2012 23:23:28 30-OCT-2012 23:26:32 YES
2653897 30-OCT-2012 23:26:32 30-OCT-2012 23:26:49 YES
2653898 30-OCT-2012 23:26:49 30-OCT-2012 23:31:05 YES
2653899 30-OCT-2012 23:31:05 31-OCT-2012 00:00:41 YES
2653900 31-OCT-2012 00:00:41 31-OCT-2012 00:31:04 YES
2653901 31-OCT-2012 00:31:04 31-OCT-2012 01:01:03 YES
2653902 31-OCT-2012 01:01:03 31-OCT-2012 01:31:17 YES
Edited by: user8875620 on Nov 8, 2012 11:20 PM

user8875620 wrote:
Hi all,
I am building a new standby.
It is brand new, and I have turned on the managed recovery for the first time after restoring my database.
--> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
Why does the first line show "NO" for applied log? (and all the logs after it shows "YES"?)
Is there something wrong, or can I ignore this as it is normal?
SQL> SELECT sequence#, first_time, next_time, applied
FROM v$archived_log
ORDER BY sequence#; 2 3
SEQUENCE# FIRST_TIME NEXT_TIME APP
2653893 30-OCT-2012 23:03:21 30-OCT-2012 23:03:25 NO
2653894 30-OCT-2012 23:03:25 30-OCT-2012 23:23:04 YES
2653895 30-OCT-2012 23:23:04 30-OCT-2012 23:23:28 YES
2653896 30-OCT-2012 23:23:28 30-OCT-2012 23:26:32 YES
2653897 30-OCT-2012 23:26:32 30-OCT-2012 23:26:49 YES
2653898 30-OCT-2012 23:26:49 30-OCT-2012 23:31:05 YES
2653899 30-OCT-2012 23:31:05 31-OCT-2012 00:00:41 YES
2653900 31-OCT-2012 00:00:41 31-OCT-2012 00:31:04 YES
2653901 31-OCT-2012 00:31:04 31-OCT-2012 01:01:03 YES
2653902 31-OCT-2012 01:01:03 31-OCT-2012 01:31:17 YES
Edited by: user8875620 on Nov 8, 2012 11:20 PMWhat is the version you are using?
Are you using Data Guard broker?
Assuming you are not using Real-time apply.
Basically there are so many bugs with the views specific to Data Guard they are v$archived_gap, v$archived_log depending on the environments.
One of note for this bug.
'APPLIED'-Column not updated if Heartbeat-ARCH hangs [ID 1369630.1]
v$archived_log: applied column is not marked if recovery applied the redo from SRL [ID 1481927.1]
Thanks

ZCM 11 Group Policies not applying to satellite servers

Hi there
We are running 2 Windows 2012 Primary Servers and a SQL 2012 Database server at our main site, all remote sites have SLES11 SP2/OES11 SP1 as satellite servers. We upgraded all servers last weekend to 11.3.1 and now have an issue with Group Policies applying to the satellites. The satellites are all set up the same with Authentication, Collection, Content and Imaging roles.
Since we upgraded Group Policies are (99% of the time) not applying on satellite sites. I have tried manually replicating content (I assume policies will come from content replication?) to the satellites - I've done this with a zac cdp replicate and zac cvc and everything seems to replicate over however I tried highlighting a satellite server and clicking on Action, Specify Content - select the Policy that is not applying and move it into the selected Content to update column and when I click finish I get the error "The Wizard cannot continue for the following reason(s): Unable to complete your request for the following reason: Error updating content"
On a managed device at the satellite site if you look at the properties of the Zenworks agent and click on Policies it has applied 4 device assigned policies successfully - Remote Management, Power Management, Application Launcher Config and Application Control Policy, also has successfully applied 3 out of the 4 User Assigned Policies - Mandatory Profile, Dynamic Local User, Application Control - but not the Windows Group Policy.
Our PCs are on Windows 8.1 and all policies were applying fine before the weekend upgrade......
Has anyone else had any experience of Group Policies not applying that could point me where to look? I have logged an SR with Novell through our reseller but as yet I am getting no response back at all, not even asking me for more information.
Many thanks
Sharon

Sounds like you have a content replication issue more than a GPO issue.
Especially if the GPO works for locations that point to the Primaries
for Content.
Do you have throttling configured anywhere in any fashion?
You may need to increase the Replication Timeout to make sure content is
getting over to the Sats. Often increasing from 60 to 240 helps, but
watch out for throttling preventing content replication.
It is possible things are backing up.
On 7/31/2014 8:26 AM, shazzypoos wrote:
>
> I should add that when you looked at the "Click for Details" to the
> right of the Effective "Failed" status the message is "Policy
> Enforcement Failed : The action (0) threw an exception. Message (1).
> Exception (2) (grouppolicy, "None of the source locations could be
> found"
>
> Hmmmm! Currently in closest server rules there is only the server for
> the site it's on set - we do not want it to come back to the Primary for
> policies. As I say, this was working before the weekend upgrade. Thanks!
>
>
Craig Wilson - MCNE, MCSE, CCNA
Novell Technical Support Engineer
Novell does not officially monitor these forums.
Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.

Acrobat Pro 10 Actions Not Applying Fast Web View

Acrobat Pro 10 actions are pretty useful overall, however they are not applying Fast Web View all the time. In my opinion, all PDFs generated today should be Fast Web View by default, but among the many applications which allow for PDF creation, not all apply Fast Web View for some reason.
I did see http://forums.adobe.com/message/3335827for a potential band-aid fix. Unfortunately, it did not work for me.
Here is the text from my Action sequence file:
<</Commands [/c << /0 [/c << /Config [/c <<   /UIPolicy [/i 3]
>>]
/HandlerName [/a /FlattenOCGs]
/Params [/c <<>>]
/Title [/t ()]
>>]
/1 [/c << /Config [/c <<   /UIPolicy [/i 3]
>>]
/HandlerName [/a /ReduceFileSize]
/Params [/c <<   /RFSCompatibility [/i 6]
>>]
/Title [/t (Reduce File Size)]
>>]
/2 [/c << /Config [/c <<   /UIPolicy [/i 3]
>>]
/HandlerName [/a /ExamineDocCmd]
/Params [/c <<   /RmAnnots [/b false]
   /RmAttachments [/b false]
   /RmBookmarks [/b false]
   /RmDeletedContent [/b true]
   /RmFormFields [/b true]
   /RmHiddenLayers [/b true]
   /RmHiddenText [/b false]
   /RmLinksActionsJS [/b false]
   /RmMetadata [/b false]
   /RmOverlappingObjects [/b false]
   /RmSearchIndex [/b false]
>>]
/Title [/t (Remove Hidden Information)]
>>]
>>]
/Input [/c << /FileVariation [/i 3]
>>]
/Output [/c << /AddToBaseName [/b false]
/DontOverwrite [/b false]
/EmbedIndex [/b false]
/FileVariation [/i 2]
/HandleOutput [/b true]
/NumbericNaming [/b false]
/OptimizePDF [/b true]
/PresetName [/t (test2)]
/RunPDFOptimizer [/b true]
>>]
>>
As you can see, the "/OptimizePDF [/b true]" is set per the instructions in the aforementioned link. It still does not set Fast Web View all the time. I ran a test of the action on a batch of 10 PDFs, some were set to Fast Web View and some were not. While one of the PDFs that was not set to Fast Web View was open in Acrobat, I ran the same Action again and it did apply Fast Web View! I even installed the latest patch hoping that would fix it, but unfortunately it did not. Distiller does in fact set Fast Web View, but it won't work on PDFs. The only way I can find to guarantee the establishment of Fast Web View is to manually do a Save As on every file which I think is asking a bit much when you deal with hundreds of PDFs on any given day. Also that would effectively defeat the purpose of running an Action on hundreds of PDFs in the first place.
Any ideas?

There is a bug because of which fast web view is always disabled. While that is fixed, here the workaround. Save the action and open the .sequ file in Notepad. Change:
                /OptimizePDF [/b false]
to
                /OptimizePDF [/b true]

OBIEE not applying outer join syntax to filters

(Note: I've already thoroughly searched the forums before posting this. Thanks)
My problem is the following:
I'm trying to build a report that is a count from my fact table, grouped by month from my date dimension for a given year, resulting in 12 data points. The problem is that not all months have actual data, but I still need those months to show on the report with a count of zero. Typical simple reporting requirement.
I have already done the obvious and within my business layer made the join between my fact table and my date dimension an outer join on the fact side, just like you'd do if writing the query by hand. And when tested by hand this includes all dates for the year anyway, and when coupled with the appropriate null test on the count measure I'd get my 12 data points with zeros were appropriate.
The problem is that there are additional filters I need to apply on the fact data (there are a couple text-based code values that didn't warrant full tables themselves so are just degenerate dimensions directly on the fact table.)
When these filters are applied at the Answer level, I'm only getting back the months that actually have data, and lose the months where the count should be zero. A check of the session log for the query that was generated shows the problem. While OBI properly generates the outer-join syntax for the join itself between the two tables (my date dim and fact table) it does NOT apply the outer-syntax to the constant-based filter against the fact, effectively negating the outer join.
Actual query from the log (I simply changed the table aliases from the ugly T##### stuff OBI generates to something more readable for posting here):
select D.DT_MONTH_NAME as c1,
D.DT_MONTH_NUM as c2,
I.INC_TYPE as c3,
I.INC_EMP_GROUP as c4,
sum(case when I.INC_KEY is null then 0 else 1 end ) as c5
from DATE_DIM D, INCIDENT_F I
where ( D.DATE_KEY = I.DATE_KEY (+) ) and ( D.DT_YEAR = 2010 and I.INC_EMP_GROUP = 'CONTRACTOR' )
group by D.DT_MONTH_NUM, D.DT_MONTH_NAME, I.INC_TYPE, I.INC_EMP_GROUP
order by c2
You can see that the outer syntax (+) is applied to the join, but not to the filter on I.INC_EMP_GROUP. If I take this query and drop it in something like SQL Developer, it only returns the months with data. If I throw the (+) after I.INC_EMP_GROUP like I'd do if writing this by hand, the desired zero-months results pop back in.
I have already searched the forums and while lots of people seem to have asked this question, the only solutions involve things like trickery in the business layer using dummy fact tables followed by manipulations at the report level etc. Unfortunately I can't rely on these as the system is eventually to be turned over to users who can't be expected to apply various hacks to write reports.
Anyone ever get to the bottom of getting OBI to apply outer join logic in filters as well, when the filtered table is meant to be outer-joined to?
Any comments are appreciated.
John

I know that this thread is a bit old thought it might be helpful to some one...
The Issue is, when using Degener@teDimen$ion ( this is !nner joned to FACT tables in BMM) and if any of the dimensions {other than theDegener@teDimen$ion (Let us say Dim X) } have an ()uter join to any of the fact tables, and you were doing your analysis using Degener@teDimen$ion, Dim X, Measure value you will face the following issues.
when filtering the analysis on the ()uter join dimension ( Dim X), the IN filter will not work. Reason is that the filter is getting applied to both the Dimension and FACT tables and the values that exist in Dimension Dim X but not in FACT table wont show up.
The above issue can be fixed by changing the join between the fact and Degener@teDimen$ion from inner to outer. I think this is a bug.. because it is supposed to filter the fact table after the entire outer joined result is obtained but not filter the fact table for the Dim X values and do a outer join. I think the BI should be intelligent enough.

Urgent Group Policy Issue - not applying despite saying it does

Thank you for this urgent help. Auditors checking this out tomorrow morning.
We have a GPO that sets the eventlog audit settings for success or failure security events. The scope is set to Authenticated Users.
When I run the group policy wizard in GPMC it shows the settings applying to one of our servers in that OU.
When I run gpresult/z from that server it shows the policy applying to that server.
But when I go into gpedit.msc the security audit settings are all set to "not defined" and they are grayed out so I can't edit them manually.
As a test I set the GPO to deny applying to that server. I ran gpudpate/force on the system and then gpresult and it shows the GPO now not applying. But the settings are still set to not defined and still not editable. they are not being set by any other GPO.
In the event logs I only see three GPO errors but they are unrelated. A separate GPO is having issues creating user accounts. No other GPOs apply.
Quick help would be fantastic.
Server runs on Windows Server 2008 R2 (I can edit GPO but not the domain ones and I don't have access to the domain controllers).

OK, After several hours I figured it out. Turns out there's bugs and odd functionality.
If someone ever tested the 'advanced audit settings' (which I did in the same GPO at some point) then it sets a registry key to disable the use of the older basic audit settings. But when you stop using those advanced settings in your GPO it doesn't remove
that registry bit. So I used the GPO to undo that setting. This was the first step. This is found Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options > "Audit: Force audit policy subcategory
settings (Windows Vista or later) to override audit policy category settings" to DISABLED.
Even though this is done, sometimes the GPO files on the domain controllers don't remove the old audit settings. So in the comments of another thread I found out you may have to go to
\\domain-fqdn\SYSVOL\domain-fqdn\Policies\{your-policy-id-where-this-setting-was-originally-set}\Machine\Microsoft\Windows NT\ and delete the Audit folder which is left behind due to some odd bug. If you don't do this even after doing the next step the
next gpupdate will bring that security setting above back down.
Next you have to reset your audit settings on your PC to the defaults. Unfortunately there is no way to do this. Auditpol /clear does not accomplish this. The only way to do this is to take the audit settings from another working system, export them and
then 'restore' those same settings to the affected server. To do this:
1. On 'working system' run cmd.exe as administrator and export the audit settings to a folder like this:
auditpol /backup /file:c:\working-auditpol-settings.txt
2. Copy that file to the broken system such as the C:\ drive and run this on the broken system:
auditpol /restore /file:c:\working-auditpol-settings.txt
Open GPEDIT.MSC and verify the audit settings are back to normal. Computer Configuration > Windows Settings > Security Settings > Local Policies > Audit Policy
Then run gpupdate/force on the formerly broken system. Close gpedit.msc and reopen and verify the settings were not overwritten. If you skipped the sysvol audit folder deletion step they may come back.
Hope this helps someone.

Changes are not applying to the reports

hi all
i have moved the RPD and catalog file to UAT there i got few changes
i did the changes in DVE and again i moved the changed reports to UAT ,but the report changes are not applied in UAT
so i again i copied same RPD and catalog to UAT now it is working fine,
why the changes are not applied to the reports that i have moved to UAT
is it mandatory to move RPD and catalog to the other environment ??
Thanks

Hi,
if you change even the filters and column names you cant modify only reports and place them in UAT,if you want to cnahge that way there is a tool CAF follow this link how to do that process
http://debaatobiee.wordpress.com/category/obiee/setup-and-environment/
If not you need to deploy RPD and catalog into UAT.
By,
KK

X does not apply to your selection because it is not inherited...

Hi
I'm trying to design a website using HTML and CSS. I have done the basic layout of the website using Div tags. However, the middle column of the website is showing up differently in Dreamweaver compared to on a browser.
I have researched the problem and found that it is caused by an error occuring on the middle column and the wrapper tag not applying to it: "x does not apply to your selection because it is not inherited. It is applied to an enclosing tag".
The code for my web page is here:
http://pastebin.com/DfXLL7Zb
This is my CSS styles code:
http://pastebin.com/81u476zE
Any help would be appreciated.
Cheers

This tells me you have unbalanced opening and closing <div> tags somewhere in your document.
Use the validation tools to check your code.
Code Validation Tools
CSS - http://jigsaw.w3.org/css-validator/
HTML - http://validator.w3.org/
In the web forums, you can mark this discussion as answered.
Nancy O.
Alt-Web Design & Publishing
Web | Graphics | Print | Media Specialists
http://alt-web.com/
http://twitter.com/altweb

Bug with min function applied to an attribute?

Does anyone know if there is a bug with the minimum function when it is applied to an attribute?
I have Accounts, Date, Sales Type and volume in my request.
I have applied min(Date) in the fx of the Date column.
My query is hitting the YAGO table even though non of the columns i am using is mapped onto a YAGO table.
As a test I've removed the min function frem the Date column and applied it to the Account column.
Again my query hits the YAGO table.
Does anyone know if it is a bug or can someone propose a workaround?
I am using OBIEE version 10.1.3.4.1090414.1922 on Windows XP.

Hi,
You can create a separate report and refer it into the column of main report by 'Filter based on results of another request'
This should resolve
Hope this helps
Regards
MuRam

Logical column not in hierarchy is shown as being drillable?

I have a hierarchy created, lets say customer. Within all the levels, logical column "customer zipcode" is not added. By default then, this column would be associated with the detail or lowest level. When I create a report in answers with just this column, it shows up drillable whereby it drills to the lowest level which is apart of by default. So my question is why is this logical column drillable if it is not associated explicitly in the hierarchy?

Thanks for the reply. Later yesterday I figured out the problem. It took some unit testing and trial and error; but, this is what I gathered during testing.
1. logical columns for hierarchy table source that are not explicitly added to a level in the hierarchy is by default put in lowest level and they are not drillable because of that.
2. If you add a logical column which is derived off other logical columns through an expression (for example concatenating col_nm||'('||col_cd||')' in the lowest level, add it as a key and set the key for "use for drilling" then this too will make all logical columns drillable to that. Don't know why but could be a bug.
3. If you set preferred drill path for the lowest level to another hierarchy level, then those logical column(s) will be drillable. Probably because they are not at the lowest level any more since there is another level down now due to the preferred drill path.
So in the end since the lowest level drillable column has to be a logical column which is built through expression and the fact that this lowest level needs to drill to another level in another hierarchy due to business requirements I am stuck with all columns not in the hierarchy being drillable. The fix around this though is to go to all these columns that are now drillable, set the aggregation rule to 'no interaction' and save as system-wide default.

Archived redolog not applied in real-time : IN-MEMORY

I created a DataGuard configuratiion in Oracle 11g so that the archived redolog are applied in real-time using the log writer.
It seems to me that the last one is not applied : when consulting the v$archived_log table the last entry have the colunm applied to "IN-MEMORY" :
select THREAD#, SEQUENCE#,APPLIED, deleted from v$archived_log;
THREAD# SEQUENCE# APPLIED DEL
1 1935 YES NO
1 1936 IN-MEMORY NO
The Oracle 11g documentation say that if "IN-MEMORY" that mean not applied in the datafile.
Could someone help me to fix it ?
Why the last archived redolog is always "IN-MEMORY" ? Is there a way to change it ?

Please check the value of the column REGISTRAR and APPLIED for the logs in the standby database.
standby database:
select sequence#,registrar,applied from v$archived_log;
If REGISTRAR = RFS and APPLIED = NO, then the log file has been received but has not yet been applied.
If REGISTRAR = RFS and APPLIED = IN-MEMORY, then the log file has been applied in memory, but the datafiles have not yet been updated.
If REGISTRAR = RFS and APPLIED = YES, then the log file has been applied and the datafiles have been updated.
Try Cancelling the Managed Recovery Process and bounce the standby database

4.0EA3 Bug - UK Column Not Applied on Entity

Similar Messages

Maybe you are looking for