Linux

First of all you need to cancel the standby recover process which will apply all the archivelogs and files on the standby side. This can be done by the following command:

SQL> recover managed stanbdy database cancel;

Afterwards you need to adjust the file management parameter to be able to manual change those files:

SQL> alter system set STANDBY_FILE_MANAGEMENT=MANUAL;

Since you already created the logfiles for the standby and the primary as pointed out. You need to shutdown the Standby database at this point, this is not a big deal incase the Standby will ask for all the missing files once it ist started up again.

SQL> shutdown immediate;

To be able to access the file that the standby thinks is in use at this moment, you need to set the following line within your init-file:

*.log_file_name_convert='dummy','dummy';

Restart your standby database.

startup mount;

And now you can drop your logfile goups like this:

SQL> ALTER DATABASE DROP LOGFILE GROUP X;

Now the file and group that has a problem should be deleted and you can recreate it:

ALTER DATABASE
ADD LOGFILE GROUP X ('$PATH/logfile1a.log', '$PATH/logfile1b.log')
SIZE XXXM REUSE;

At this point your standby database should be able to use the file again.

OperatingSystem:

ProgrammingLanguage:

Technology:

I use virtual machine on my computer, and I don't have these problems. It is much easier than having dual-booting.

OperatingSystem:

Reprepro is a way to solve the problem.

There is a nice tutorial on digitalocean: 'https://www.digitalocean.com/community/tutorials/how-to-use-reprepro-for...' on how to publish your packages.

It contains following instructions:

* Prepared and published a repository signing key
* Set up a repository with Reprepro, the repository manager
* Made the repository public with the web server Nginx
* Added the repository on another server

OperatingSystem:

Because the application is multithreaded and the error is occuring at high load-times, I realized that the application is not thread safe and that is probably the cause. So I looked into my classes and entities and realized that one class is not thread-safe because it has two attributes that were not accessed and edited in a thread safe way. The solution in java was to use Atomic classes for example AtomicInteger and to change the value using methods of this class. This way we make the class thread safe and NullPointerException is solved.

OperatingSystem:

ProgrammingLanguage:

Taggings:

OperatingSystem:

OperatingSystem:

SocialTags:

Taggings:

OperatingSystem:

ProgrammingLanguage:

Technology:

There are many different possibilities to answer this question. We will go top down beginning with the browser.
Most of the browsers support the html input tag of type "email" and most of them would automatically warn the user about a wrong format of the address. However there are many standards of email address pattern. Furthermore the user might disable the browser validation, so we should not rely on this.
The second station is the javascript of the browser. Probably the easiest way to validate the email address is to use a regular expression an match the input against this expression. However the user may disable the javascript or send a request in other way than browser. Therefore it's absolutely necessary to validate the email address on the server side. This might be done by a regular expression, but some more sophisticated systems would check the MX record of the domain given in the email address, to be sure it might be a real address of a real mail server.

OperatingSystem:

ProgrammingLanguage:

Technology:

Use automated UI Test, which is possible with the Selenium library and a browser driver. The browser driver allows us to run actions in a browser while writing code. The Selenium library is an interface to connect many browsers with the same code base. So now we are able to code a simple test, where a robot is automatically clicking through the website and trying out the login functionality. This technique may also apply to test other important and high priority UI features.

OperatingSystem:

Group conversations on Skype faulty, if one member's OS is Linux

The solution to this issue is very simple and trivial. The issue itself is a known problem in the community and many users experience it. Since Skype for Linux 4.3 is the newest available main version, uninstalling and reinstalling does not seem to help the problem.
In July 2016, Skype has introduced Skype Linux Alpha. Whilst this version seems to support group chats for users of various operating systems, it's alpha version still makes it unreliable if consistency is needed, e.g. professional purposes such as job interviews.

I have solved this problem by resolving to Skype's web version. Logging in with your account, enables the group conversation seamlessly, without the need to create a new group. Although group conversations are now possible, accepting an invite to share a screen does not seem to work herein.

Taggings:

Pages

Subscribe to Linux