Search results for query: *

Our revenue coding structure used for recording income and operating costs comprises 15 digits structured in 4 segments as follows:- Segment 1 Function / Site / Dept [5 digits 1 alpha 4 numerics] Segment 2 Process [3 digits 1 alpha 2 numerics] Segment 3 Activity...

sandylou, As it is a backup you have, you won't be able to attach it, but should be able to restore it, as Jeff says.

Thanks for your input Paul. I'm now thinking that I'll use EVA snapshots of the filesystem and mount them on the reporting server to report against. I think this will be quicker and easier than using the SQL tools available.

I've just noticed that Enterprise Edition is required to take database snapshots. As I only have Standard Edition I guess I need to find an alternative solution to the one Paul suggests. I'm thinking it's goint to have to be transactional replication where it only 'syncronises' once a night...

Thanks Paul, Does anyone have a link to a document / support note which describes how best to setup and configure a mirror and subsequent snapshot?

Hi, I would appreciate any tips/advice on options for providing a separate copy of a SQL 2005 database, on a separate server, for reporting against. This is for performance reasons. The following information describes my situation; - I have a database of about 80GB - The reporting 'copy' only...

We also found that our newer CICS middleware has 'lost' the options for host trace and debug however there is an easy way to get it back. Try using Alt-q when the Ellipse login box is on the screen - it works for me!

We are using eac31_11. We are already limited to 8 characters due to enhanced security. Was it easy to set up, i.e following the advice above?

Thanks Ivangent. Is there a way to deal with users who do not have an AD entry, i.e. share a PC login with others? Does this work with Citrix clients? Regards

Ellipse 5.2.3.7 offers, via the EAC, the choice to use external authentication instead of the usual username and password. We are in the early stages of considering using LDAP for this. Has anyone tried using this? What steps are required? And above all, does it work? Thanks

Thanks Drew. We will be using IBM's TX-Series for Ellipse but your points are still valid. Does anyone else have any experience of Ellipse on NT4?

Drw, Have you, or anyone else, run Ellipse on an NT client and if so what problems did you have (if any) and what version of Ellipse was it. Thanks

Does the Ellipse client run on NT4 Workstation? Does Mincom support this? Your replies are eagerly awaited. Thank you.

Does anyone know MIMS 4.3.1.2 version of the countusr.sh script mentioned by Dianne001 - or a copy of the code behind it. Thanks

chibag, This is what we are already doing. It's against this read only copy that we have performance issues using CorVu. Any help / advice relating to improving prformance? Thanks

Hi We are using the standby database approach for updating our reporting database. Each evening the archived redo logs are copied and applied. Currently we are doing this from one HP-UX11 server to another, with Oracle 8.1.6 What I would like to know is; although not recommended, is it...

Hi We have quite a large database - e.g. our database is almost 50Gb with indexes and table msf900 has over 14 million rows. We are running 4.3.1.2 with Oracle 8.1.6 on a UNIX HP-UX11 platform. We regularly have in excess of 200 concurrent users. We have up to 30 CorVu connections at a time...

Thanks Alan - certainly food for thought. I presume when you say the retirement of 4.3 you mean all versions, including 4.3.1.2

Hi I am getting hundreds of context errors appearing in my error.log Here is a small section.... ERROR: updateContext(208) failed - entry not allocated ERROR: retrieveContext(208) failed - entry not allocated ERROR: updateContext(208) failed - entry not allocated ERROR: updateContext(208)...

Glen, Thanks for the info you provide. I cannot believe that Mincom will not provide a fix for this problem as surely they wouldn't/couldn't cope with all the forced upgrades to Ellipse in the required timescale - May 2006.