Activity overview
Latest activity by aosala
                    
                      
                        Hi! I ran the update and did not face the same error anymore when running the same compares. Seems to have fixed the issue! Thanks! / comments
                        
                        
                        
                      
                      
                      
                
                  Hi! I ran the update and did not face the same error anymore when running the same compares. Seems to have fixed the issue! Thanks!
                      
                    
                  
                    
                      
                        Don't know if this helps, but here is something I discovered:  
-- Version 4.0.7.207  
-- Index  is shown as a new object in source (DB) compared to scripts folder 
-- => When I try to update this to script folder "Item with the same name" error occurs  
CREATE UNIQUE INDEX dw.pk_idx ON dw.tablename(id) 
NOCOMPRESS LOGGING TABLESPACE tablespacename;  
-- Same time the create table script looks like this in our scripts folder. This doesn't pop up when I compare DB to the scripts folder.  
CREATE TABLE dw.tablename ( 
CONSTRAINT pk PRIMARY KEY (id) USING INDEX dw.pk_idx 
) NOCOMPRESS 
LOGGING 
TABLESPACE tablespacename;   
-- Version 4.0.0.14 
-- The new index dw.pk_idx is not shown at all when comparing DB to our scripts folder (not as new or changed item)  
-- Index is added to the create table script, which is changed compared to the one in our scripts folder: 
CREATE TABLE dw.tablename ( 
CONSTRAINT pk PRIMARY KEY (id) USING INDEX (CREATE UNIQUE INDEX dw.pk_idx ON dw.tablename(id) NOCOMPRESS LOGGING TABLESPACE tablespacename) 
) NOCOMPRESS 
LOGGING 
TABLESPACE tablespacename; / comments
                        
                        
                        
                      
                      
                      
                
                  Don't know if this helps, but here is something I discovered:
-- Version 4.0.7.207
-- Index  is shown as a new object in source (DB) compared to scripts folder
-- => When I try to update this to sc...
                      
                    
                  
                    
                      
                        I'm having exactly the same problem. I'm comparing indexes in a database to a script folder, and every time I try to update the script folder, I get that same error saying an item with the same key already exists. This seems to happen with all the indexes involved in the comparison. It doesn't matter if the create script for the index already exists in the target folder or if it's a completely new index in the DB.  
I also sent an error report to you guys.  
PS. Version is the same 4.0.7.207 / comments
                        
                        
                        
                      
                      
                      
                
              I'm having exactly the same problem. I'm comparing indexes in a database to a script folder, and every time I try to update the script folder, I get that same error saying an item with the same key...