Transactional Replication Not replicating non-clustered Indexes

Hi
I have created a transactional replication.I am sure that I have configured it to replicate Non-Clustered indexes,
but It does not do so.
I tried several times to reinitialize the subscription,but still no luck.
Regards

It is True for sure.
But the problem is solved.I had to wait until the Initialize process get completed.
But I am sure that this problem happened before.Sometimes it works fine but sometimes not.
Hi ArashMasroor,
According to your description, it seems that you encounter the issue that non-clustered indexes property is reset to “False” sometimes.
To work around this issue, you can use a post-replication SQL script to create the indexes. Whatever articles you’re publishing open up the indexes drop down list of the article in object explorer, right-click on an index and levitate over Script Index as,
then Create-to, then click New Query Window editor.
Up will pop up a new query window with the resulting index. Work your way through all the indexes on all the articles of the publication, copy and pasting just the create index line and below of each script, pull them all together into one query window.
Once you’re done find a safe folder somewhere on your hard drive and save the SQL query as an .sql file with a sensible name. Then you can execute this script after applying the Snapshot. For more details, please review this
blog.
There is also a similar thread for your reference.
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/b0f3870d-1a65-4384-a17b-96825ec5f098/transactional-replication-nonclustered-indexes-not-copying?forum=sqlreplication
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

Similar Messages

Transactional Replication - Not replicating

Hello,
I've recently set up transactional replication from one database in Server 1 to another database in server 2.
I've checked the Replication Monitor and they stay green with Latency 0.02 sec and not showing any issues.
However when I inserted a row on the database on Server 1 and waiting 1 minute it's not replicating on Server 2 database.
Could anyone advise what and where to check for issues?
Best regards,
Mohan

What is the latency now? Does it show higher latency?
Could you confirm if the table in which you inserted the row is part of replication?
Could you also try inserting a "tracer token" and see if it replicates and how much time it takes?
http://technet.microsoft.com/en-us/library/ms151846(v=sql.105).aspx
Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

Transactional Replication: Non-Clustered Indexes not copying.

Hello,
I set up replication on our servers at work to streamline some procedures we run daily/weekly on them.
This copies around 15 articles from two databases on the "Master" server to another server used for execution purposes. For the most part it was a pretty straight forward task and it seemed to work nicely; but I realised after some investigation that the
non-clustered indexes weren't copying over to the child server.
I set the non-clustered indexes property in the properties of the publishing articles to "True" and generated a new snapshot, this seemed to work, but I've come into work this morning to find the property has reset to "False" and I have no indexes on the
table again. Why is this happening and is there any way I can resolve the matter so the indexes are copied over concurrently?
Thanks in advance for your advice.
JB

I actually solved this.
You can use a post-replication SQL script to create the indexes. Whatever articles you're publishing open up the indexes drop down list of the article in object explorer, right-click on an index and hover over Script Index as, then Create-to, then click
New Query Window editor.
Up will pop up a new query window with the resulting index. Work your way through all the indexes on all the articles of the publication, copy and pasting just the create index line and below of each script, pull them all together into one query window.
Once you're done find a safe folder somewhere on your harddrive and save the SQL query as an .sql file with a sensible name.
Right click on the publication and goto properties. Click on the "Snapshot" tab, in there; there should be a section saying "Run additional scripts". Choose the browse button next to "After applying the Snapshot; execute this script:"
Navigate to your script file and choose it. Once done click ok and it'll prompt you that something has changed and if you'd like to generate a new snapshot, make sure you do or it won't work.
That's it, you'll find once the publication has bulk copied over the the subscriptions successfully there are non clustered indexes on the tables. Pretty simple!

Non Clustered Indexing not working for SQL server 2005

I have create two non clustered index on two particular tables. Now the problem is its working fine..but after restarting my server its working stop and then again I have to delete that index and recreate it.

try these links
http://blog.sqlauthority.com/2009/02/07/sql-server-introduction-to-force-index-query-hints-index-hint/
http://blog.sqlauthority.com/2009/02/08/sql-server-introduction-to-force-index-query-hints-index-hint-part2/
http://www.brentozar.com/archive/2013/10/index-hints-helpful-or-harmful/
Hope it Helps!!

What is RID in non clustered index and its use

Hi All,
I need help regarding following articles on sql server
1) what is RID in non clustered index and its use.
2) What is Physical and virtual address space. Difference in 32 bit vs 64 bit Virtual address space
Regards
Rahul

Next time Please ask single question in a thread you will get better response.
1. RID is location of heap. When you create Non clustered index on heap and
lookup happens to get extra records RID is used to locate the records. RID is basically Row ID. This is basic definition for you. Please read
this Thread for more details
2. I have not heard of Physical address space. I Know Virtual address space( VAS)
VAS is simple terms is amount of memory( virtual ) 'visible' to a process, a process can be SQL Server process or windows process. It theoretically depends on architecture of Operating System. 32 bit OS will have maximum range of 4 G VAS, it's calculated
like a process ruining on 32 bit system can address max up to 2^32 locations ( which is equivalent to 4 G). Similarly for 64 bit max VAS will be 2^64 which is theoretically infinite. To make things feasible maximum VAS for 64 bit system is kept to 8 TB. Now
VAS acts as layer of abstraction an intermediate .Instead of all request directly mapping to physical memory it first maps to VAS and then mapped to physical memory so that it can manage request for memory in more coordinated fashion than allowing process
to do it ,if not it will soon cause memory crunch.Any process when created on windows will see virtual memory according to its VAS limit.
Please read
This Article for detailed information
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

Space occupied by clustered index Vs non-clustered index

I am trying to understand the indexes. Does clustered index occupy more space than a non-clustered index because it carries the information about rest of the other columns also. Could you guys please help me understand this. Thanks in advance.
svk

Hi czarvk,
Clustered index in SQL Server takes up more space than non-clustered indexes.
Clustered index arranges the way records are stored in a table putting them in order (key, value), all the data are sorted on the values of the index.
A non-clustered index is a completely different object in a table, containing only a subset of columns and a row locator to the table’s rows or to the clustered index’s key.
So clustered index in SQL Server takes up more space than non-clustered indexes.
If you have any question, please feel free to let me know.
Regards,
Donghui Li

Unity Connection 8.5.1 directory replication not working between clusters

Last night we deleted 10 users from one cluster (there are 10 networked together), with the intention of moving them to another site on another cluster. The users deleted without error, however when we did a search on other clusters the users were still appearing as remote. We have seen this before and ran the command line to delete the globalusers from each cluster. We then proceeded to add the users to the destination cluster without issue. This morning I have noted that none of the other 9 clusters are aware of these new users. I did push out the directory under intrasite links however it is still in the "in progress" state after 12 hours.
Can anyone tell me what service is tied to this function or how I can restart this process or fix this? I will open a TAC ticket as I suspect we may need some additional steps as this is not the first directory replication issue we have seen over the years.

Thanks Rob, I did know about this bug and have dealt with it before. I have been able to workaround this for years now (these clusters deployed 2011), however I have never experienced an issue where the added users did not replicate out to other servers. Another bullet in my list of reasons why we need to upgrade these versions.

Session not replicated in clustered oc4j instances

The application is deployed to two clustered oc4j instances(A and B) and is configured to use PEER replication protocol. After logging into the application(say A handled the request, created and stored a user object in http session), we shutdown A, and click on application link, the request is routed to B, but B shows no user object in http session is found, this happens in a servlet filter. Could somebody provide some suggestions why?

Hmm, OK. Then we need to dig in a little further.
Can you post what the orion-application.xml file looks like for these applications?
It has the <cluster> tag set in it.
You can find it in $ORACLE_HOME/j2ee/home/application-deployments/<app-name>
Are these clustered OC4J instances on the same server -- if so, did you set allow-colocation="false", which would prevent the replica from being stored on the same physical host, and thus not be avaialble when you need it?
You can enable logging for the clsuter session manager -- you can acess the logging propeties page in ASC and then set the "oracle.j2ee.cluster" to the FINEST level to start pumping some log messages into the log file.
Note: in 10.1.3.0 the settings are not persisted when made via ASC -- you have to enter them manually in the j2ee/<instance-name>/config/j2ee-logging.xml file. In 10.1.3.1 the settings are persisted automatically into this file.
The easiest way to see the log messages in the file is using the Log Viewer function in ASC as well. Look for the "Diagnostics" log in the particular Oc4J instance where the app is deployed.
cheers
-steve-

Deployment Plan not replicating across clusters

I am deploying application in clustred environment, where Admin and one ms are in one physical box and other Managed Server is in another physical box.
When redoplying the application after making few changes, viz:
1. Updating the resource file.
2. Updating the deployment paln file.
3. Upgrading the application, this changes are working in only one managed server but not in the other managed server which is other physical box. Once you manually copy the deployment paln file, the second managed server also reflects the changes.
Even bouncing the server, will not reflect the changes.
Any suggestions?

RAC supports a mixture of storage types.. raw, file system and ASM.
I believe you can have several options..
1. you can continue to maintain your FLASH on ASM with the RMAN backups only going to the shared filesystem location
2. can maintain the RMAN backups on ASM and then when you backup from disk to tape (D2T) you can restore from tape to populate the development /test environments
3 like you say can maintain the entire FLASH area on shared file system.
When sharing a common area between development, test and production environments with some these critical files? hmmm! security & safety of files comes to my mind as a concern..
You have not mentioned the O/S details,,, however the cost factor involved in having a third party file system in the mix should also be considered.

Impact of creating a non-clusterd index on a huge transaction table?

Hello Everyone,
We have a transaction table containing 10 million records and everyday a million records will be inserted. We don’t have any clustered index on this table as this is a transaction table (more than 10 columns to uniquely identify a row). We
do have some SPs which in turn some reports getting generated using this table. In order to improve the performance of an SP, we created a non-clustered index on this table and we found a huge performance gain.
Here comes my question - will this (creation of non-clustered index) impacts my table data load performance or other reports generation?
Any suggestions will be appreciated.
Many Thanks!
Rajasekhar.

Hello Rajasekhar,
First identify this table and corresponding columns usage. Through SP_depends system procedure you can identify this table dependencies.
Then look at complex queries and it's execution plans. You can get an output recommendations of appropriate missing indexes.
Now you can try to create appropriate indexes. Always I suggest you to limit the index count if you are inserting/updating large volume records. Also if possible create clustered index.
One more option, you can horizontally partitioned the table and move data to multiple filegroups. Based of range of data your query performance also improve a lot.
To apply partition for existing table, you should take backup and recreate from scartch.
Check this link : http://www.mssqltips.com/sqlservertip/2888/how-to-partition-an-existing-sql-server-table/
Best Regards,
Ashokkumar.
Ashokkumar

How do I set access 2002 Upsizing Wizard to create clustered-index on SQL 2005

Here is an extract from the Acc2Sql2.doc >>
By default, the Upsizing Wizard
transfers all indexes as nonclustered indexes. You can modify the Upsizing
Wizard to transfer the primary key index to a clustered index. To make this
change, start Microsoft Access and open the upsizing wizard library database.
For Microsoft Access 95, the filename is Wzcs.mda. For Microsoft Access 97, the
filename is Wzcs97.mda. When the database is open, click the Modules tab and open the
UT_ModUserConstants module. Search down to the UT_CLUSTERED constant. Change
the default value from False to True.
<<< end quote
Question: I am using ACCESS 2002 upsize wizard, I searched my computer for *.mda and could not find any wzcs*.mda. How do I set it so that it creates clustered-index instead of non-clustered-index?

Hi,
This question is not related to the forum. This is a question regarding MS-ACCESS.
[Personal Site] [Blog] [Facebook]

Large tables without clustered indexes -- a bad idea, or ok?

We have several large tables that don't have clustered indexes, but do have primary keys and assorted other indexes. We're seeing issues that look like they are related to statistics even though there is a nightly update statistics job.
So my question is, does the existence of a clustered index impact other indexes or the update statistics process? Are our tables ok the way they are?
Adding clustered indexes would be a big project for non-development-related reasons so I would need to have good reasons to advocate for this.

RSingh,
"By default" is a confusing word here. If you do it with WIZARD, I agree. But with T-SQL,there is no space for by default, it can be anything.
I agree that I assumed here as I wont do much things with wizard. :)
Try the below:
--Here by default, its non-clustered
create table Test_table(Col1 int , Col2 int not null )
Create clustered index IX__Test_Table on Test_Table (Col1)
Alter table test_Table
Add Constraint PK_testTable
Primary Key (Col2);
Drop table test_table
--Here by default, its clustered
create table Test_table(Col1 int , Col2 int not null Primary key)
Create index IX__Test_Table on Test_Table (Col1)
Drop table test_table
Neither the word "By Default" is a confusing word nor it happens only in WIZARD. Let me clarify below. I said "When a primary key constraint is created it creates a unique clustered index by default". Run the below DDL and check whether
a clustered index is created or not. i.e
CREATE TABLE Persons
P_Id int NOT NULL,
LastName varchar(255) NOT NULL,
FirstName varchar(255),
Address varchar(255),
City varchar(255),
CONSTRAINT pk_PersonID PRIMARY KEY (P_Id,LastName)
Regards, RSingh
That did not really make any sense to my context as I am NOT against that it will create Clustered index, In fact, my code says the same. My point is only "By default" is confusing.
Let me explain, what I mean "By default"....
Create index IX_Indexname on Tablename(Colname)
The above will create "non clustered index" BY DEFAULT. Any situation, the above would create only non-clustered irrespective of other indexes present in the table.
Hope the above is clear. May be its my way looking at "BY DEFAULT".

SQL Server 2014 Bug - with Clustered Index On Temp Table with Identity Column

Hi,
Here's a stored procedure. (It could be shorter, but this will show the problem.)
CREATE PROCEDURE dbo.SGTEST_TBD_20141030 AS
IF OBJECT_ID('TempDB..#Temp') IS NOT NULL
DROP TABLE #Temp
CREATE TABLE #Temp
Col1 INT NULL
,Col2 INT IDENTITY NOT NULL
,Col3 INT NOT NULL
CREATE CLUSTERED INDEX ix_cl ON #Temp(Col2)
SET IDENTITY_INSERT #Temp ON;
RAISERROR('Preparing to INSERT INTO #Temp...',0,1) WITH NOWAIT;
INSERT INTO #Temp (Col1, Col2, Col3)
SELECT 1,2,3
RAISERROR('Insert Success!!!',0,1) WITH NOWAIT;
SET IDENTITY_INSERT #Temp OFF;
In SQL Server 2014, If I execute this (EXEC dbo.SGTEST_TBD_20141030) It works. If I execute it a second time - It fails hard with:
Msg 0, Level 11, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.
Msg 0, Level 20, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.
In SQL Server 2012, I can execute it over and over, with no problem. I've discovered two work-a-rounds:
1) Add "WITH RECOMPILE" to the SP CREATE/ALTER statement, or
2) Declare the cluster index in the TABLE CREATE statement, e.g. ",UNIQUE CLUSTERED (COL2)"
This second option only works though, if the column is unique. I've opted for the "WITH RECOMPILE" for now. But, thought I should share.

Hi,
I did not get any error Message:
CREATE TABLE #Temp
Col1 INT NULL
,Col2 INT IDENTITY NOT NULL
,Col3 INT NOT NULL
CREATE CLUSTERED INDEX ix_cl ON #Temp(Col2)
SET IDENTITY_INSERT #Temp ON;
RAISERROR('Preparing to INSERT INTO #Temp...',0,1) WITH NOWAIT;
INSERT INTO #Temp (Col1, Col2, Col3)
SELECT 1,2,3
RAISERROR('Insert Success!!!',0,1) WITH NOWAIT;
SET IDENTITY_INSERT #Temp OFF;
SELECT * FROM #Temp
OUTPUT:
Col1 Col2
Col3
1 2 3
1 2 3
1 2 3
Select @@version
--Microsoft SQL Server 2012 (SP1) - 11.0.3000.0 (X64)
Oct 19 2012 13:38:57
Copyright (c) Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
Thanks Shiven:) If Answer is Helpful, Please Vote

Creating a Primary Key in SSMS without Also Creating a Clustered Index

In the course of development (SQL Server Express 2012) I’m creating various tables which should not have a clustered index on the primary key. However, it seems as if SSMS is obsessed with always doing so. I cannot seem to find a way through the simple
“right click on column and select "Set Primary Key" method to stop the creation of an associated clustered index.
I can work around it fairly easily by having SSMS generate the necessary script and then changing CLUSTERED to NONCLUSTERED, but I’m curious if there is a way to do it purely using the UI that I’m overlooking…

To be honest, though, until I get much closer to production and have loaded a lot more data I won't know for sure one way or the other - this was more of an awareness question from my part and something that I could not find anyone ever asking on
the web.
To add to what David said, the performance impact in the end depends much on the size of the table size and amount of memory available to SQL Server. All things being equal, performance will be roughly the same with both sequential and random keys
as long as data are memory resident. But a random key greatly reduces the likelihood need data will be in memory.
The worst case scenario for single-row selects is an even distribution of random key values, a very large table, and little SQL Server memory. Nearly every select query will require a physical I/O in this case. Since each spinning-media disk
spindle is capable of only 150-200 IOPS so your throughput will be constrained accordingly.
A big advantage of sequential key values for single-row selects is improved temporal reference locality. In practice, the most recently inserted/accessed rows are most likely to be subsequently queried. A single-row query will not only
read the requested row, but the adjacent rows on the same page as well, thus avoiding costly I/O for a select of those rows.
See http://www.dbdelta.com/improving-uniqueidentifier-performance/ for an example of how to generate sequential GUIDs from C# code.
Dan Guzman, SQL Server MVP, http://www.dbdelta.com

ASSERTION FAILED of replica-related stub in a non-clustered SLSB

Wl 6.1 sp2
Solaris 2.8
We have 50 SLSBs running on non-clustered WL servers. Yet we are seeing
the following ASSERTION FAILED error, which from the stacktrace seems to
hint the ejb stub is doing something cluster-related... I have attached
ejb-jar.xml of the offending bean; someone please verify we are not
building cluster-capable stubs, and if we are building the right stub,
please explain why the exception is happening. Thanks!
******** STACKTRACE
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Assertion
violated ]
at weblogic.utils.Debug.assert(Debug.java:74)
at weblogic.rmi.cluster.BasicReplicaList.reset(BasicReplicaList.java:175)
at
weblogic.rmi.cluster.PrimarySecondaryReplicaHandler.setPiggybackResponse(Pri
marySecondaryReplicaHandler.java:94)
at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.setPiggybackResponse(ReplicaAware
RemoteRef.java:294)
at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
:265)
at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
:229)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy14.getStatus(Unknown Source)
at
com.go2.dtc.service.AccountStatus.accountIsOnline(AccountStatus.java:57)
******* EJB-JAR.XML
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise
JavaBeans 2.0//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
<ejb-jar>
<enterprise-beans>
<session>
<ejb-name>accountservice.AccountServiceHome</ejb-name>
<home>com.go2.ejb.services.accountservice.AccountServiceHome</home>
<remote>com.go2.ejb.services.accountservice.AccountService</remote>
<ejb-class>com.go2.ejb.services.accountservice.AccountServiceBean</ejb-class
>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>accountservice.AccountServiceHome</ejb-name>
<method-intf>Remote</method-intf>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>accountservice.AccountServiceHome</ejb-name>
<method-intf>Remote</method-intf>
<method-name>getStatus</method-name>
<method-params>
<method-param>java.lang.String</method-param>
</method-params>
</method>
<trans-attribute>NotSupported</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>accountservice.AccountServiceHome</ejb-name>
<method-intf>Remote</method-intf>
<method-name>changeSearchListingStatus</method-name>
<method-params>
<method-param>int</method-param>
<method-param>java.lang.String</method-param>
</method-params>
</method>
<trans-attribute>RequiresNew</trans-attribute>
</container-transaction>
</assembly-descriptor>
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise
JavaBeans 2.0//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
<ejb-jar>
<enterprise-beans>
<session>
<ejb-name>accountservice.AccountServiceHome</ejb-name>
<home>com.go2.ejb.services.accountservice.AccountServiceHome</home>
<remote>com.go2.ejb.services.accountservice.AccountService</remote>
<ejb-class>com.go2.ejb.services.accountservice.AccountServiceBean</ejb-class
>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>accountservice.AccountServiceHome</ejb-name>
<method-intf>Remote</method-intf>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>accountservice.AccountServiceHome</ejb-name>
<method-intf>Remote</method-intf>
<method-name>getStatus</method-name>
<method-params>
<method-param>java.lang.String</method-param>
</method-params>
</method>
<trans-attribute>NotSupported</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>accountservice.AccountServiceHome</ejb-name>
<method-intf>Remote</method-intf>
<method-name>changeSearchListingStatus</method-name>
<method-params>
<method-param>int</method-param>
<method-param>java.lang.String</method-param>
</method-params>
</method>
<trans-attribute>RequiresNew</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>

Hi Rajesh,
This error was reported on our QA system error log, and only occurred a
couple of times in a very specific time frame. I will ask QA again if it
has happened since the first report.
However, even if this bug is minor and not production-worthy, what I am more
concerned about is the fact that the stacktrace seem to indicate the bug is
cluster-related, when we set our SLSBs to be non-clustered. Can someone
please confirm, given the ejb-jar.xml and weblogic-ejb-jar.xml I've posted
below, that I have properly configured and deployed our beans to be
non-clustered? I don't want to introduce cluster overhead (and cluster
bugs) when we don't need to!
Gene
"Rajesh Mirchandani" <[email protected]> wrote in message
news:[email protected]...
The reason I asked you if it is readily reproducable is because I had seenthis
issue (support case) in WLS 6.1(no sp). The problem there was that itcould not
be reproduced again and so I did not analyze it further.
Is this happening under load ?
Gene Chuang wrote:
Hi Rob,
AccountStatus is calling AccountService, which is a SLSB. I have
attached
its ejb-jar.xml in my original post, and here's the corresponding
weblogic-ejb-jar.xml:
!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic6.0.0
EJB//EN' 'http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd'>

<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>accountservice.AccountServiceHome</ejb-name>
<stateless-session-descriptor>
<pool>
<max-beans-in-free-pool>100</max-beans-in-free-pool>
</pool>
<stateless-clustering>
<stateless-bean-is-clusterable>False</stateless-bean-is-clusterable>
>>
>>
<stateless-bean-methods-are-idempotent>False</stateless-bean-methods-are-ide
mpotent>
</stateless-clustering>
</stateless-session-descriptor>
<transaction-descriptor>
<trans-timeout-seconds>300</trans-timeout-seconds>
</transaction-descriptor>
<jndi-name>accountservice.AccountServiceHome</jndi-name>
</weblogic-enterprise-bean>
<transaction-isolation>
<isolation-level>TRANSACTION_READ_COMMITTED</isolation-level>
<method>
<ejb-name>accountservice.AccountServiceHome</ejb-name>
<method-intf>Remote</method-intf>
<method-name>*</method-name>
</method>
</transaction-isolation>
</weblogic-ejb-jar>
"Rob Woollen" <[email protected]> wrote in message
news:[email protected]...
It looks like AccountStatus is calling a stateful session bean that
uses
in-memory replication. (The PrimarySecondary stub is only used forin-memory
replicated sfsb.)
Do you have any sfsb?
-- Rob
Gene Chuang wrote:
Wl 6.1 sp2
Solaris 2.8
We have 50 SLSBs running on non-clustered WL servers. Yet we are
seeing
the following ASSERTION FAILED error, which from the stacktrace
seems to
hint the ejb stub is doing something cluster-related... I haveattached
ejb-jar.xml of the offending bean; someone please verify we are not
building cluster-capable stubs, and if we are building the rightstub,
please explain why the exception is happening. Thanks!
******** STACKTRACE
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[Assertion
violated ]
at weblogic.utils.Debug.assert(Debug.java:74)
atweblogic.rmi.cluster.BasicReplicaList.reset(BasicReplicaList.java:175)
at
weblogic.rmi.cluster.PrimarySecondaryReplicaHandler.setPiggybackResponse(Pri
marySecondaryReplicaHandler.java:94)
at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.setPiggybackResponse(ReplicaAware
RemoteRef.java:294)
at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
:265)
at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
:229)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy14.getStatus(Unknown Source)
at
com.go2.dtc.service.AccountStatus.accountIsOnline(AccountStatus.java:57)
>>>>
******* EJB-JAR.XML
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise
JavaBeans 2.0//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
<ejb-jar>
<enterprise-beans>
<session>
<ejb-name>accountservice.AccountServiceHome</ejb-name>
<home>com.go2.ejb.services.accountservice.AccountServiceHome</home>
><remote>com.go2.ejb.services.accountservice.AccountService</remote>
<ejb-class>com.go2.ejb.services.accountservice.AccountServiceBean</ejb-class
>>>>>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>accountservice.AccountServiceHome</ejb-name>
<method-intf>Remote</method-intf>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>accountservice.AccountServiceHome</ejb-name>
<method-intf>Remote</method-intf>
<method-name>getStatus</method-name>
<method-params>
<method-param>java.lang.String</method-param>
</method-params>
</method>
<trans-attribute>NotSupported</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>accountservice.AccountServiceHome</ejb-name>
<method-intf>Remote</method-intf>
<method-name>changeSearchListingStatus</method-name>
<method-params>
<method-param>int</method-param>
<method-param>java.lang.String</method-param>
</method-params>
</method>
<trans-attribute>RequiresNew</trans-attribute>
</container-transaction>
</assembly-descriptor>
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise
JavaBeans 2.0//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
<ejb-jar>
<enterprise-beans>
<session>
<ejb-name>accountservice.AccountServiceHome</ejb-name>
<home>com.go2.ejb.services.accountservice.AccountServiceHome</home>
><remote>com.go2.ejb.services.accountservice.AccountService</remote>
<ejb-class>com.go2.ejb.services.accountservice.AccountServiceBean</ejb-class
>>>>>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>accountservice.AccountServiceHome</ejb-name>
<method-intf>Remote</method-intf>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>accountservice.AccountServiceHome</ejb-name>
<method-intf>Remote</method-intf>
<method-name>getStatus</method-name>
<method-params>
<method-param>java.lang.String</method-param>
</method-params>
</method>
<trans-attribute>NotSupported</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>accountservice.AccountServiceHome</ejb-name>
<method-intf>Remote</method-intf>
<method-name>changeSearchListingStatus</method-name>
<method-params>
<method-param>int</method-param>
<method-param>java.lang.String</method-param>
</method-params>
</method>
<trans-attribute>RequiresNew</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>--
Rajesh Mirchandani
Developer Relations Engineer
BEA Support

Transactional Replication Not replicating non-clustered Indexes

Similar Messages

Maybe you are looking for